Methods and apparatus for wireless data traffic management in wireline backhaul systems

ABSTRACT

Methods and apparatus for enhancing performance of a wireline communication network backhaul for wireless nodes based on data traffic and node characterization. In one embodiment, the node comprises a small-cell or other wireless base station (e.g., one utilizing unlicensed or quasi-licensed spectrum such as CBRS or C-Band) that is backhauled by a DOCSIS system within a managed HFC network, and the methods and apparatus utilize such factors as traffic load, geographic or topological location, node technology type, and user device profile for each node to determine scheduling of traffic over the wireline transmission medium used for the delivery of services. In another embodiment, the foregoing factors can be weighted for further determination related to an assignment of the time slots or other resources for the delivery of services.

RELATED APPLICATIONS

This application is related to co-owned and co-pending U.S. patentapplication Ser. No. 16/996,496 filed Aug. 18, 2020 and entitled“METHODS AND APPARATUS FOR WIRELESS DEVICE ATTACHMENT IN A MANAGEDNETWORK ARCHITECTURE,” Ser. No. 16/997,776 filed Aug. 19, 2020 andentitled “METHODS AND APPARATUS FOR COORDINATION BETWEEN WIRELINEBACKHAUL AND WIRELESS SYSTEMS,” and Ser. No. 16/995,407 filed Aug. 17,2020 and entitle “METHODS AND APPARATUS FOR SPECTRUM UTILIZATIONCOORDINATION BETWEEN WIRELINE BACKHAUL AND WIRELESS SYSTEMS,” each ofwhich is incorporated herein by reference in its entirety.

COPYRIGHT

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent files or records, but otherwise reserves all copyrightrights whatsoever.

BACKGROUND 1. Technological Field

The present disclosure relates generally to the field of data networksand wireless equipment, and specifically, in one or more exemplaryembodiments, to methods and apparatus for wireless and wireline networkinfrastructure coordination including characterization of data trafficand wireless nodes, and allocation of backhaul bandwidth based thereon.

2. Description of Related Technology

Data communication services are now ubiquitous throughout user premises(e.g., home, office, and even vehicles). Such data communicationservices may be provided via a managed or unmanaged networks. Forinstance, a typical home has services provided by one or more networkservice providers via a managed network such as a cable or satellitenetwork. These services may include content delivery (e.g., lineartelevision, on-demand content, personal or cloud DVR, “start over,”etc.), as well as so-called “over the top” third party content.Similarly, Internet and telephony access is also typically provided, andmay be bundled with the aforementioned content delivery functions intosubscription packages, which are increasingly becoming more user- orpremises-specific in their construction and content. Such services arealso increasingly attempting to adopt the paradigm of “anywhere,”“anytime,” so that users (subscribers) can access the desired services(e.g., watch a movie) via a number of different receiving and renderingplatforms, such as in different rooms of their house, on their mobiledevice while traveling, etc.

Similarly, wireless data services of varying types are now ubiquitous.Such wireless services may include for instance (i) “licensed” service,such as cellular service provided by a mobile network operator (MNO),(ii) quasi-licensed (e.g., “shared” spectrum which in some cases may bewithdrawn, such as CBRS), (iii) unlicensed (such as Wi-Fi (IEEE Std.802.11) and “unlicensed cellular” technologies such as LTE-U/LAA orNR-U, as well as IoT (Internet of Things) services.

One common model is to provide localized unlicensed “small cell” (e.g.,3GPP “femtocell”) coverage via a service provider such as a terrestrialfiber or cable MSO. These small cells can leverage e.g., 3GPP unlicensedbands (such as NR-U bands in the 5 GHz range) or other spectrum such asCBRS (3.550-3.70 GHz, 3GPP Band 48), and C-Bands (3.30-5.00 GHz).Technologies for use of other bands such as 6 GHz band (5.925-7.125 GHzsuch as for Wi-Fi-6), and even mmWave bands (e.g., 24 GHz and above) arealso under development and expected to be widely deployed in comingyears.

Small cells offer great flexibility for providing effectivelyshared-access cellular coverage without the CAPEX and otherconsiderations associated with a normal licensed cellular (e.g., 3GPPNodeB) deployment. Since small cells are designed to service fewerusers/throughput, they can also be backhauled by many existing andcommonly available forms of infrastructure, such as coaxial cablenetworks currently managed and operated by cable MSOs. Advantageously,there is a very large base of installed coaxial cable in the U.S. (andother countries), and the cable medium itself is capable of appreciablebandwidth, especially with more recent upgrades of the backhaulinfrastructure supporting the coaxial cable “last mile” (e.g., DWDMoptical distribution networks, high-speed DOCSIS modem protocols, andconverged/edge cable platforms such as CCAP).

Hence, cable MSOs have more recently begun deploying “small cells” (suchas CBRS CBSDs) for their enterprise and residential customers in orderto provide wireless coverage and backhaul, whether in high-density urbanapplications, suburban applications, and even low-density ruralapplications. For instance, in rural applications, such wireless cellsin effect greatly extend the last mile of installed cable, providing awireless backhaul for e.g., residential CPE which could otherwise not beserviced due to lack of a coaxial cable. Conversely, in urbanapplications, wireless coverage may be spotty due to e.g., largebuildings and other infrastructure, and poor coverage can affect largenumbers of users due to their higher geographical/spatial density,thereby necessitating small cell use. Common to all of these deploymentscenarios is the managed backhaul (e.g., cable) network.

Managed Cable Networks

Network operators deliver data services (e.g., broadband) and videoproducts to customers using a variety of different devices, therebyenabling their users or subscribers to access data/content in a numberof different contexts, both fixed (e.g., at their residence) and mobile(such as while traveling or away from home).

Data/content delivery may be specific to the network operator, such aswhere video content is ingested by the network operator or its proxy,and delivered to the network users or subscribers as a product orservice of the network operator. For instance, a cable multiple systemsoperator (MSO) may ingest content from multiple different sources (e.g.,national networks, content aggregators, etc.), process the ingestedcontent, and deliver it to the MSO subscribers via e.g., a hybrid fibercoax (HFC) cable/fiber network, such as to the subscriber's set-top boxor DOCSIS cable modem. Such ingested content is transcoded to thenecessary format as required (e.g., MPEG-2 or MPEG-4/AVC), framed andplaced in the appropriate media container format (“packaged”), andtransmitted via e.g., statistical multiplex into a multi-programtransport stream (MPTS) on 6 MHz radio frequency (RF) channels forreceipt by the subscribers RF tuner, demultiplexed and decoded, andrendered on the user's rendering device (e.g., digital TV) according tothe prescribed coding format.

FIG. 1 is functional block diagram illustrating a typical prior artmanaged (e.g., HFC cable) content delivery network architecture 100 usedto provide such data services to its users and subscribers, specificallyshowing a typical approach for delivery of high-speed data (broadband)services to such users via a variety of different end-userconfigurations.

As shown in FIG. 1 (simplified for illustration), one or more networkheadends 102 are in fiber communication with a plurality of nodes 113via fiber ring and distribution network 121. The headend(s) include aDOCSIS-compliant CMTS (cable modem termination system) 103, discussed ingreater detail below, which provide for downstream and upstream datacommunication with a plurality of user or subscriber DOCSIS cable modems(CMs) 125 which service corresponding CPE 127 such as WLAN devices, PCs,wireless small cells, etc. The nodes 113 convert the optical domainsignals to RF signals typically in the range of 42-750 MHz fordownstream transmission, and likewise convert RF domain signals tooptical for upstream data in the range of 0-42 MHz. Within the coaxialportion of the network 100, a plurality of amplifiers 114 and tap-offpoints 115 exist, so as to enable amplification and delivery of signals,respectively, to all portions of the coaxial topography. A backbone 119connects the headend to external networks and data sources, such as viathe Internet or other types of MAN/WAN/internetworks.

DOCSIS

In a typical HFC network headend 102 (see FIG. 1A), data is packetizedand routed to the requesting user based on the user's network or IPaddress, such as via the aforementioned high-speed DOCSIS cable modems125, according to the well-known network-layer and DOCSIS PHY protocols.

The CMTS 103, is the central platform in enabling high speed Internetconnectivity over the HFC network. The CMTS consists of variousfunctional components, including upstream and downstream transceivers,MAC schedulers, QoS functions, security/access authentication, etc.

Another key component in the headend 102, is the Edge QAM modulator(EQAM) 105. The EQAM receives e.g., an IP unicast or multicast MPEGtransport stream packet over a GigE (Gigabit Ethernet) interface, andproduces transport stream on one or more RF channels for transmissionover the HFC distribution network 121. The EQAM can also perform otherfunctions such as re-stamp of Program Clock Reference (PCR) timestampssuch as for de-jitter processing. Output from the EQAM 105 is combinedwith video signals (e.g., SDV, analog, etc.) for downstream transmissionby the combiner logic 107.

While DOCSIS 3.0 is currently the prevailing technology, DOCSIS 3.1 israpidly being deployed as an upgrade to DOCSIS 3.0. DOCSIS 3.1 bringsmany fundamental changes, including Orthogonal Division Multiplexing(OFDM) as the new PHY layer modulation technology. In OFDM technology,the data is converted from serial to parallel, and transmitted onmultiple orthogonal carriers simultaneously. Using the orthogonalmulti-carrier concept of OFDM modulation improves the downstream andupstream throughput significantly, and reduces the receiver complexityin the CM and CMTS. Furthermore, bounding narrow band subcarriers inOFDM allows creation of wide band channels from 24 MHz to 192 MHz,moving away from legacy 6 MHz (or 8 MHz) channels of the type used intraditional DOCSIS 3.0/EuroDOCSIS deployments.

See FIG. 2A, wherein the typical DOCSIS 3.0 allocation 200 includesbroadband spectrum 204 at a frequency above the spectrum 202 used forbroadcast television, SDV, VoD, and other traditional “video” services.Spectrum utilization is also increased in DOCSIS 3.1, up toapproximately 1.2 GHz. FIG. 2B is a simplified graphical representationof DOCSIS 3.1 spectrum allocations; note that traditional DOCSIS 3.0 andQAM technology (i.e., non-OFDM-based modulation) can be used alongsidethe newer OFDM-based modulation schemes.

Another feature introduced in DOCSIS 3.1, is the Low Density ParityCheck Code (LDPC) in upstream and downstream to optimize efficiency,provide robustness against narrow band interferers, and burst errors.The LDPC decoding efficiencies ostensibly increase the Signal-to-Noiseratio (SNR), allowing to use higher modulation for upstream anddownstream. Prior to DOCSIS.31, the highest order modulation to allowreliable transmission were 64-QAM for upstream, and 256-QAM fordownstream. Due to the LDPC error correcting efficiencies, the DOCSIS3.1 standard supports 4096-QAM in downstream, and 1024-QAM in upstream,allowing the data transmission speed close to the theoretical limits.

FIG. 2C is a tabular representation of frequency bands associated withprior art cable systems including broadband (DOCSIS 4.0). DOCSIS 4.0,which is the latest specification for data transmission over cable as ofthe date of this writing, leverages the DOCSIS 3.1 technology to expandthe downstream and upstream spectrum to use full spectrum available forcable network (5 MHz to approximately 1.8 GHz), which is about 600 MHzmore than the 1.2 GHz available under DOCSIS 3.1. The Extended SpectrumDOCSIS (EDX) is designed to work over existing cable infrastructure.

DOCSIS 4.0, which is the latest specification for data transmission overcable as of the date of this writing, leverages the DOCSIS 3.1technology to expand the downstream and upstream spectrum to use fullspectrum available for cable network (0 to approximately 1.8 GHz), whichis about 600 MHz more than the 1.2 GHz available under DOCSIS 3.1. SeeFIG. 3C. The Extended Spectrum DOCSIS (EDX) is designed to work overexisting cable infrastructure.

Full Duplex (FDX), another feature introduced in DOCSIS 4.0, will allowupstream and downstream traffic to occupy the same part of spectrum,thus doubling the throughput by using the existing HFC networkcharacteristics.

CBRS and Other “Shared Access” Systems

In 2016, the FCC made available Citizens Broadband Radio Service (CBRS)spectrum in the 3550-3700 MHz (3.5 GHz) band, making 150 MHz of spectrumavailable for mobile broadband and other commercial users. The CBRS isunique, in that it makes available a comparatively large amount ofspectrum (frequency bandwidth) without the need for expensive auctions,and without ties to a particular operator or service provider.

Moreover, the CBRS spectrum is suitable for shared use betweengovernment and commercial interests, based on a system of existing“incumbents,” including the Department of Defense (DoD) and fixedsatellite services. Specifically, a three-tiered access framework forthe 3.5 GHz is used; i.e., (i) an Incumbent Access tier 302, (ii)Priority Access tier 304, and (iii) General Authorized Access tier 306.See FIG. 3. The three tiers are coordinated through one or more dynamicSpectrum Access Systems (SAS) 402 as shown in FIG. 4 (including e.g.,Band 48 therein).

Incumbent Access (existing DOD and satellite) users 302 includeauthorized federal and grandfathered Fixed Satellite Service (FSS) userscurrently operating in the 3.5 GHz band shown in FIG. 3. These userswill be protected from harmful interference from Priority Access License(PAL) and General Authorized Access (GAA) users. The sensor networks,operated by Environmental Sensing Capability (ESC) operators, make surethat incumbents and others utilizing the spectrum are protected frominterference.

The Priority Access tier 304 (including acquisition of spectrum for upto three years through an auction process) consists of Priority AccessLicenses (PALs) that will be assigned using competitive bidding withinthe 3550-3650 MHz portion of the band. Each PAL is defined as anon-renewable authorization to use a 10 MHz channel in a single censustract for three years. Up to seven (7) total PALs may be assigned in anygiven census tract, with up to four PALs going to any single applicant.Applicants may acquire up to two-consecutive PAL terms in any givenlicense area during the first auction.

The General Authorized Access tier 306 (for any user with an authorized3.5 GHz device) is licensed-by-rule to permit open, flexible access tothe band for the widest possible group of potential users. GeneralAuthorized Access (GAA) users are permitted to use any portion of the3550-3700 MHz band not assigned to a higher tier user and may alsooperate opportunistically on unused Priority Access License (PAL)channels.

The FCC's three-tiered spectrum sharing architecture of FIG. 3 utilizes“fast-track” band (3550-3700 MHz) identified by PCAST and NTIA, whileTier 2 and 3 are regulated under a new Citizens Broadband Radio Service(CBRS). CBSDs (Citizens Broadband radio Service Devices—in effect,wireless access points) 131 (see FIG. 4) can only operate underauthority of a centralized Spectrum Access System (SAS) 402. Rules areoptimized for small-cell use, but also accommodate point-to-point andpoint-to-multipoint, especially in rural areas.

Under the FCC system, the standard SAS 402 includes the followingelements: (1) CBSD registration; (2) interference analysis; (3)incumbent protection; (4) PAL license validation; (5) CBSD channelassignment; (6) CBSD power limits; (7) PAL protection; and (8)SAS-to-SAS coordination. As shown in FIG. 4, these functions areprovided for by, inter alia, an incumbent detection (i.e., environmentalsensing) function 407 configured to detect use by incumbents, and anincumbent information function 409 configured to inform the incumbentwhen use by another user occurs. An FCC database 411 is also provided,such as for PAL license validation, CBSD registration, and otherfunctions.

An optional Domain Proxy (DP) 408 is also provided for in the FCCarchitecture. Each DP 408 includes: (1) SAS interface GW includingsecurity; (2) directive translation between CBSD 131 and domaincommands; (3) bulk CBSD directive processing; and (4) interferencecontribution reporting to the SAS.

A domain is defined is any collection of CBSDs 131 that need to begrouped for management; e.g.: large enterprises, venues, stadiums, trainstations. Domains can be even larger/broader in scope, such as forexample a terrestrial operator network. Moreover, domains may or may notuse private addressing. A Domain Proxy (DP) 408 can aggregate controlinformation flows to other SAS, such as e.g., a Commercial SAS (CSAS,not shown), and generate performance reports, channel requests,heartbeats, etc.

CBSDs 131 can generally be categorized as either Category A or CategoryB. Category A CBSDs have an EIRP or Equivalent Isotropic Radiated Powerof 30 dBm (1 Watt)/10 MHz, fixed indoor or outdoor location (with anantenna <6 m in length if outdoor). Category B CBSDs have 47 dBm EIRP(50 Watts)/10 MHz, and fixed outdoor location only. Professionalinstallation of Category B CBSDs is required, and the antenna must beless than 6 m in length. All CBSD's have a vertical positioning accuracyrequirement of +/−3 m. Terminals (i.e., user devices akin to UE) have 23dBm EIRP (0.2 Watts)/10 MHz requirements, and mobility of the terminalsis allowed.

In terms of spectral access, CBRS utilizes a time division duplex (TDD)multiple access architecture.

FIG. 5 illustrates a typical prior art CBRS-based CPE (consumer premisesequipment)/FWA architecture 500 for a served premises (e.g., userresidence), wherein the CPE/FWA 503 is backhauled by a base station(e.g., eNB or gNB) 131, the latter which is backhauled by the DOCSISnetwork shown in FIG. 1A. A PoE (Power over Ethernet) injector system404 is used to power the CPE/FWA 403 as well as provide Ethernet (packetconnectivity for the CPE/FWA radio head to the home router 405).

Additionally, new wireless systems and small cells are being fielded,including in new frequency bands (see e.g., FIG. 6A, illustrating newBand 71 with the 600 MHz region, and FIG. 6B showing e.g., Bands 12-17in the 700 MHz region).

Unaddressed Issues of Resource Allocation and Usage

As described previously, the CM and CMTS are the two main components inDOCSIS backhaul systems. The CM receives/transmits the signal from/tothe CMTS, and provides data services to premises. The CMTS controls andmanages CMs deployed within the network. Furthermore, the CMTS specifiesdifferent service flows for different traffic types, and each serviceflow may be associated with a given modulation type in the downlink anduplink.

The DOCSIS MAC protocol utilizes as one option a “best efforts”request/grant mechanism to coordinate transmission between multiple CMs125. If a CM needs to transmit anything on the upstream channels, itfirst must request that the CMTS allocate resources to the CM. The CMTS103 allocates the resources for the transmission of data to the CMs inthe next upstream frame(s) if bandwidth is available, such as via anupstream bandwidth allocation (MAP) message.

Furthermore, the CMTS must assign at least one service flow to each CM125 to carry best-effort traffic. In order to support different traffictypes, the CMTS may assign multiple service flows to each CM, with eachflow having its own characteristics and traffic parameters.

In a typical “strand” based wireless network deployment model such asthose rural and urban scenarios previously described, a base stationsuch as a CBRS CBSD (which typically is configured to utilize 3GPP LTEor 5G NR “Node B” technology and protocols as the basis for itsoperation) is backhauled to the network operator core (and MNO core ifrequired) by the MSO's DOCSIS network; i.e., via a CM 125, as shown inFIG. 1A. The CBSD/xNB communicates to the CMTS 103 to transmit andreceive traffic via the interposed CM 125.

However, in this strand network deployment model, since the CBSD/xNBuses the existing backhaul for data connectivity to other networks,there can be noticeable loss of data throughput/speed and increasedlatency in both the downstream (DS or DL) and the upstream (US or UL),especially in highly congested areas. This results in large part fromeach CM 125 sharing one or more common CMTS 103 and other backhaulinfrastructure, and for the UL, the foregoing request/grant cycle forobtaining upstream bandwidth.

Moreover, opportunities for congestion of the network backhaulingwireless base stations and other devices are increasing due to expansionof wireless services and use of small cells such as CBSDs. This is truesince, inter alia, (i) multiple base stations may be backhauled by acommon CMTS (see FIG. 1B, wherein multiple different CBSD/xNB devices131 serving heterogeneous types of users/clients are backhauled to acommon CMTS); and (ii) extant DOCSIS protocols do not have higher-levelvisibility as to either the presence of wireless base stations as CM“clients”, nor the particular aspects of user or client devicesaccessing such wireless base stations for their own backhaul (e.g., usersmartphones/tablets, FWA devices as in FIG. 5, vehicle telematicssystems, or other cellular-enabled devices). In that base stations mayact as “load multipliers” from the perspective of the backhaul due totheir expanded wireless coverage area and accessibility to a variety ofdifferent types of devices, as their use expands within the serviceprovider network, the potential resulting load and congestion increasesdisproportionately. As discussed above, newer generations of DOCSISsystems make use of expanded frequency ranges and OFDM technology (e.g.,up to 1.2 GHz for DOCSIS 3.1, and 1.8 GHz for DOCSIS 4.0); however, suchadvanced technologies are only being implemented incrementally, and evenwhen fully implemented, allocation of limited DOCSIS backhaul resourcesmay be critical due to e.g., increased pervasiveness of ultra-highbandwidth and low-latency technologies such as 5G NR (includingincipient mmWave variants thereof, which can operate at tremendouslyhigh data rates).

As can be appreciated, such congestion within the DOCSIS backhaul maymanifest itself as a variety of undesirable conditions or symptoms, suchas increased packet loss and retransmission requests, reduced datathroughput, increased data latency, inability to maintain QoE or QoSrequirements, or failed timing requirements (such as e.g., failure tocomplete UE to EPC/5GC core attachment and setup functions due tolatency). These conditions can lead to reduced user experience orsatisfaction with the service provider's services.

Hence, improved apparatus and methods for coordination between thewireline (e.g., DOCSIS) backhaul and the deployed base stations (andother devices) served by that backhaul are needed, especially withregard to fair and informed allocation of backhaul bandwidth toindividual devices based on their configuration and anticipated oractual requirements.

SUMMARY

The present disclosure addresses the foregoing needs by providing, interalia, methods and apparatus for scheduling and coordination between awireless base station and its wireline backhaul.

In a first aspect of the disclosure, a computerized method of operatinga packet network infrastructure comprising a plurality of packetreceiver apparatus and at least one packet transmitter apparatus isdescribed. In one embodiment, the method includes:

obtaining data at respective ones of the plurality of packet receiverapparatus from wireless equipment connected thereto, each of theobtained data comprising data relating to a plurality of configurationaspects of the wireless equipment; and causing data relating to theobtained data to be transmitted to the at least one packet transmitterapparatus, the transmitted data configured to enable the at least onetransmitter apparatus to determine scheduling of radio frequency (RF)channels utilized by the packet network infrastructure for communicationbetween the plurality of packet receiver apparatus and the at least onepacket transmitter apparatus.

In one variant, the method further comprises: identifying at the atleast one packet transmitter apparatus, the wireless equipment connectedto one of the plurality of packet receiver apparatus; and based at leaston the identifying, causing a change in a weighting assigned to the onepacket receiver apparatus, the change in the weighting affecting thescheduling. In one implementation, the identifying at the at least onepacket transmitter apparatus the wireless equipment comprisesidentifying a type or configuration of a wireless base station connectedto a cable modem (CM) based at least in inspecting one or more datastructures transmitted to the CM from the wireless base station.

In another variant, the packet network infrastructure comprises a DOCSIS(data over cable service specification) packet data system, the at leastone packet transmitter apparatus comprises a cable modem terminationsystem (CMTS), and the plurality of packet receiver apparatus comprisesa plurality of cable modems (CMs).

In a further variant, the causing data relating to the obtained data tobe transmitted to the at least one packet transmitter apparatuscomprises causing transmission of data indicative of the plurality ofconfiguration aspects, the plurality of configuration aspectscomprising: (i) a number of attached user or client devices; and (ii)configuration data enabling determination of a geographic location ofthe wireless equipment. In one implementation, the infrastructurecomprises a hybrid fiber coaxial (HFC) network infrastructure; and thedetermination of scheduling of radio frequency (RF) channels utilized bythe packet network infrastructure for communication between theplurality of packet receiver apparatus and the at least one packettransmitter apparatus comprises determination of a respective quantityof resources to allocate to each of the plurality of packet receiverapparatus. For instance, the respective quantities of resources each mayinclude a respective number of downlink (DL) time slots.

In another variant, the method further comprises: obtaining second dataat respective ones of the plurality of packet receiver apparatusrelating to at least one configuration aspect of the respective packetreceive apparatus; and causing data relating to the obtained second datato be transmitted to the at least one packet transmitter apparatus, thetransmitted data relating to the obtained second data for use in thescheduling of radio frequency (RF) channels utilized by the packetnetwork infrastructure.

In one implementation, the obtaining second data at respective ones ofthe plurality of packet receiver apparatus relating to at least oneconfiguration aspect of the respective packet receive apparatuscomprises obtaining data relating to one or more devices in datacommunication with the respective packet receive apparatus and requiringbackhaul by the infrastructure.

In another aspect, a computerized network apparatus for use in a networkis disclosed. In one embodiment, the network apparatus includes: atleast one packet data interface configured for communication with aradio frequency transceiver apparatus; processor apparatus in datacommunication with the at least one packet data interface; and storageapparatus in data communication with the processor apparatus, thestorage apparatus comprising at least one computer program.

In one variant, the at least one program is configured to, when executedby the processor apparatus, cause the computerized network apparatus to:receive first data packets via the at least one packet data interface,the first data packets comprising data relating to at least (i) aconfiguration of a wireless access node, and (ii) operation of thewireless access node; evaluate the received first data packets togenerate characterization data relating a plurality of operational andconfiguration aspects of the wireless access node; and causetransmission of at least a portion of the characterization data to theradio frequency transceiver apparatus, the transmission of thecharacterization data enabling allocation by the computerized networkapparatus of resources for use by (i) at least a modem apparatusassociated with the wireless access node, and (ii) a plurality of othermodem apparatus in data communication with the radio frequencytransceiver apparatus.

In one implementation, the computerized network apparatus comprises aDOCSIS cable modem termination system (CMTS), the radio frequencytransceiver apparatus comprises a QAM (quadrature amplitude modulation)modulator, and the modem apparatus comprises a DOCSIS cable modem (CM)which is used to backhaul the wireless access node. In one versionthereof, the at least one computer program is further configured to,when executed by the processor apparatus, cause the computerized networkapparatus to transmit data to the radio frequency transceiver apparatuscausing scheduling of respective pluralities of time slots on aplurality of different RF carriers for use by respective ones of aplurality of modem apparatus including the at least modem apparatusassociated with the wireless access node, the plurality of modemapparatus having a common operational or configuration attribute. Forexample, the common operational or configuration attribute may comprisemembership in at least one of (i) a common physical service group (pSG),or (ii) a common virtual service group (vSG).

In another variant, the at least one computer program is furtherconfigured to, when executed by the processor apparatus, cause thecomputerized network apparatus to: determine that one or moreoperational criteria are met within at least a portion of aninfrastructure of the network; and based at least on the determination,transmit data to the radio frequency transceiver apparatus causing atemporary change in allocation of the resources to at least one of theplurality of modem apparatus.

In a further variant, the evaluation of the received first data packetsto generate characterization data relating a plurality of operationaland configuration aspects of the wireless access node comprisesevaluation of at least: (i) a technology type used by the wirelessaccess node; (ii) a location of the wireless access node; and (iii) anumber of user or client devices in active data communication with thewireless access node. In one implementation thereof, the evaluation ofthe technology type used by the wireless access node comprisesevaluation of whether the wireless access node is capable of wirelessoperation compliant with 3GPP (Third Generation Partnership Project) 5GNR (Fifth Generation New Radio) Standards; the evaluation of a locationof the wireless access node comprises determination of whether thewireless access node is located within a designated hotspot or highactivity area; and the evaluation of a number of user or client devicesin active data communication with the wireless access node comprisesdetermination of a number of 3GPP UE (user equipment) operating ineither RRC_Idle or RRC_Connected modes.

In a further aspect of the disclosure, computerized wireless access nodeapparatus is described. In one embodiment, the node apparatus includes:at least one first packet data interface for interface with a radiofrequency modulation/demodulation apparatus; at least one wirelessinterface for interface with one or more wireless user devices;processor apparatus in data communication with the at least one firstpacket data interface and the at least one wireless interface; andstorage apparatus in data communication with the processor apparatus,the storage apparatus comprising at least one computer program.

In one variant, the at least one program is configured to, when executedby the processor apparatus, cause the computerized wireless access nodeapparatus to: transmit data relating to at least one of a configurationor operational state of the computerized wireless access node apparatusto a network apparatus via the radio frequency modulation/demodulationapparatus, the network apparatus and radio frequencymodulation/demodulation apparatus communicative via at least onewireline radio frequency channel, the transmitted data configured toenable the network apparatus to selectively schedule data for deliveryto the radio frequency modulation/demodulation apparatus using aplurality of time-frequency resources, the plurality of time-frequencyresources selected as part of a scheduling algorithm configured to alsoschedule respective pluralities of time-frequency resources for othersof a plurality of radio frequency modulation/demodulation apparatuscommunicative with the network apparatus based at least on respectivedata relating to a configuration of a computerized wireless access nodeapparatus associated with respective ones of others of the plurality ofradio frequency modulation/demodulation apparatus.

In one implementation, the radio frequency modulation/demodulationapparatus comprises a cable modem within a hybrid fiber coax (HFC)network; the wireless access node comprises a 3GPP-compliant NodeB; andthe data relating to at least one of a configuration or operationalstate comprises data indicative of at least: (i) a technology type usedby the wireless access node; (ii) a location of the wireless accessnode; and (ii) a number of user or client devices in active datacommunication with the wireless access node.

In another implementation, the data relating to at least one of aconfiguration or operational state comprises data indicative of a weightor score derived by the wireless access node based at least one theconfiguration or operational state, and the at least one computerprogram is further configured to, when executed by the processorapparatus, cause the computerized wireless access node apparatus to:generate a request for grant of a temporary increase in resourceallocation by the network apparatus; and transmit the request to thenetwork apparatus via the radio frequency modulation/demodulationapparatus in data communication with the wireless access node.

In another aspect, a method of conducting, at a network modem apparatus,an evaluation to determine resource scheduling for a plurality ofpremises modem apparatus, is described.

In a further aspect of the disclosure, computer readable apparatusincluding a non-transitory storage medium, the non-transitory mediumincluding at least one computer program having a plurality ofinstructions is disclosed. In one embodiment, the plurality ofinstructions are configured to, when executed on a processing apparatus:receive data relating to a configuration used for transmission of databetween base stations connected to a modem and respective UE devices,and based on the received data, adjust a configuration of a plurality ofOFDM channel between a modem termination system and respective ones ofthe modem so as to achieve one or more target network operationalparameters.

In one variant, the storage apparatus includes a storage mediumconfigured to store one or more computer programs, such as on a CMTS. Inone embodiment, the apparatus includes a program memory or HDD or SSDand stores one or more computer programs.

In another aspect, an integrated circuit (IC) device implementing one ormore of the foregoing aspects is disclosed and described. In oneembodiment, the IC device is embodied as a SoC (system on Chip) device.In another embodiment, an ASIC (application specific IC) is used as thebasis of the device. In yet another embodiment, a chip set (i.e.,multiple ICs used in coordinated fashion) is disclosed. In yet anotherembodiment, the device comprises a multi-logic block FPGA device.

In another aspect, a baseband processing unit (BBU) is disclosed. In oneembodiment, the BBU is disposed within an HFC network infrastructure andis configured to interface with a plurality of distributed radio headunits at respective served premises of the HFC network in support of,inter alia, wireline backhaul resource scheduling.

These and other aspects shall become apparent when considered in lightof the disclosure provided herein.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating a prior art hybrid fiber-coaxial(HFC) data network for delivery of data to end user devices.

FIG. 1A is a block diagram illustrating the DOCSIS infrastructure of theHFC network of FIG. 1, and various types of backhauled premises devices.

FIG. 1B is a block diagram illustrating the DOCSIS infrastructure of theHFC network of FIG. 1, wherein multiple different devices servingheterogeneous types of users/clients are backhauled to a common CMTS.

FIG. 2A is a graphical representation of frequency bands associated withprior art cable systems including broadband (DOCSIS 3.0).

FIG. 2B is a graphical representation of frequency bands associated withprior art cable systems including broadband (DOCSIS 3.1).

FIG. 2C is a tabular representation of frequency bands associated withprior art cable systems including broadband (DOCSIS 4.0).

FIG. 3 is a graphical illustration of prior art CBRS (Citizens BroadbandRadio Service) users and their relationship to allocated frequencyspectrum in the 3.550 to 3.700 GHz band.

FIG. 4 is a functional block diagram illustrating a general architecturefor the CBRS system of the prior art.

FIG. 5 is a graphical illustration of a prior art configuration fordelivery of data from a base station to an end-user device (CPE/FWA)within the wireless coverage area of the base station.

FIG. 6A is a graphical representation of Band 71 radio frequency (RF)spectrum currently allocated for use by the FCC.

FIG. 6B is a tabular representation of various E-UTRA RF spectrum bandscurrently allocated.

FIG. 7 is a logical flow diagram illustrating a typical prior art dataoperational and backhaul scenario for a wireless base station (e.g.,CBSD) backhauled via the DOCSIS infrastructure of FIG. 1A.

FIG. 8 is a logical flow diagram illustrating one embodiment of ageneralized method for bandwidth allocation and scheduling for enhancedwireless base stations backhauled via the improved DOCSIS infrastructureof the present disclosure.

FIG. 8A is a logical flow diagram illustrating one implementation of thebase station configuration data collection process of the method of FIG.8.

FIG. 8B is a logical flow diagram illustrating one variant of theprocess of FIG. 8A.

FIGS. 8C-8F are logical flow diagrams illustrating one implementation ofthe base station and CMe evaluation process of FIG. 8.

FIG. 8G is a logical flow diagram illustrating one implementation of theCMe schedule determination process of FIG. 8.

FIG. 9 is a logical flow diagram illustrating another embodiment of ageneralized method for wireline bandwidth allocation and scheduling,wherein individual CMe perform collection, aggregation and evaluation ofdata.

FIG. 10 is a block diagram illustrating one exemplary embodiment ofnetwork configuration with enhanced backhaul scheduling functionalityaccording to the present disclosure.

FIG. 11 is a block diagram illustrating another exemplary embodiment ofnetwork configuration with enhanced backhaul scheduling functionalityaccording to the present disclosure.

FIG. 12 is a block diagram illustrating yet another exemplary embodimentof network configuration with enhanced backhaul scheduling functionalityaccording to the present disclosure, wherein a network-based basebandprocessing functionality is utilized.

FIG. 13 is a block diagram illustrating one exemplary embodiment ofnetwork converged headend and remote PHY device (RPD) configuration withenhanced scheduling functionality according to the present disclosure.

FIG. 14 is a block diagram illustrating one exemplary embodiment of basestation (e.g., xNBe) apparatus configured for provision of enhancedwireline scheduling functions according to the present disclosure.

FIG. 14A is a block diagram illustrating one exemplary implementation ofthe base station (e.g., xNBe) of FIG. 14, illustrating different antennaand transmit/receive chains thereof.

FIG. 15 is a block diagram illustrating one exemplary embodiment of acable modem (CMe) apparatus configured for enhanced wireline schedulingfunctions according to the present disclosure.

FIG. 16 is a ladder diagram illustrating communication and data flowbetween UE(s), xNBe, CMe, and CMTSe, according to one embodiment of thepresent disclosure.

All Figures © Copyright 2019-2020 Charter Communications Operating, LLC.All rights reserved.

DETAILED DESCRIPTION

Reference is now made to the drawings wherein like numerals refer tolike parts throughout.

As used herein, the term “access node” refers generally and withoutlimitation to a network node which enables communication between a useror client device and another entity within a network, such as forexample a CBRS CBSD, small cell, a cellular xNB, a Wi-Fi AP, or aWi-Fi-Direct enabled client or other device acting as a Group Owner(GO).

As used herein, the term “application” (or “app”) refers generally andwithout limitation to a unit of executable software that implements acertain functionality or theme. The themes of applications vary broadlyacross any number of disciplines and functions (such as on-demandcontent management, e-commerce transactions, brokerage transactions,home entertainment, calculator etc.), and one application may have morethan one theme. The unit of executable software generally runs in apredetermined environment; for example, the unit could include adownloadable Java Xlet™ that runs within the JavaTV™ environment.Applications as used herein may also include so-called “containerized”applications and their execution and management environments such as VMs(virtual machines) and Docker and Kubernetes.

As used herein, the term “CBRS” refers without limitation to the CBRSarchitecture and protocols described in Signaling Protocols andProcedures for Citizens Broadband Radio Service (CBRS): Spectrum AccessSystem (SAS)—Citizens Broadband Radio Service Device (CBSD) InterfaceTechnical Specification—Document WINNF-TS-0016, Version V1.2.1. 3,January 2018, incorporated herein by reference in its entirety, and anyrelated documents or subsequent versions thereof.

As used herein, the terms “client device” or “user device” or “UE”include, but are not limited to, set-top boxes (e.g., DSTBs), gateways,modems, FWA devices, personal computers (PCs), and minicomputers,whether desktop, laptop, or otherwise, and mobile devices such ashandheld computers, PDAs, personal media devices (PMDs), tablets,“phablets”, smartphones, and vehicle infotainment systems or portionsthereof.

As used herein, the term “computer program” or “software” is meant toinclude any sequence or human or machine cognizable steps which performa function. Such program may be rendered in virtually any programminglanguage or environment including, for example, C/C++, Fortran, COBOL,PASCAL, assembly language, markup languages (e.g., HTML, SGML, XML,VoXML), and the like, as well as object-oriented environments such asthe Common Object Request Broker Architecture (CORBA), Java™ (includingJ2ME, Java Beans, etc.) and the like.

As used herein, the term “DOCSIS” refers to any of the existing orplanned variants of the Data Over Cable Services InterfaceSpecification, including for example DOCSIS versions 1.0, 1.1, 2.0, 3.0,3.1 and 4.0 and any EuroDOCSIS counterparts or derivatives relatingthereto, as well as so-called “Extended Spectrum DOCSIS”.

As used herein, the term “headend” or “backend” refers generally to anetworked system controlled by an operator (e.g., an MSO) thatdistributes programming to MSO clientele using client devices. Suchprogramming may include literally any information source/receiverincluding, inter alia, free-to-air TV channels, pay TV channels,interactive TV, over-the-top services, streaming services, and theInternet.

As used herein, the terms “Internet” and “internet” are usedinterchangeably to refer to inter-networks including, withoutlimitation, the Internet. Other common examples include but are notlimited to: a network of external servers, “cloud” entities (such asmemory or storage not local to a device, storage generally accessible atany time via a network connection, and the like), service nodes, accesspoints, controller devices, client devices, etc.

As used herein, the term “LTE” refers to, without limitation and asapplicable, any of the variants or Releases of the Long-Term Evolutionwireless communication standard, including LTE-U (Long Term Evolution inunlicensed spectrum), LTE-LAA (Long Term Evolution, Licensed AssistedAccess), LTE-A (LTE Advanced), and 4G/4.5G LTE.

As used herein, the term “memory” includes any type of integratedcircuit or other storage device adapted for storing digital dataincluding, without limitation, ROM, PROM, EEPROM, DRAM, SDRAM,(G)DDR/2/3/4/5/6 SDRAM, EDO/FPMS, RLDRAM, SRAM, “flash” memory (e.g.,NAND/NOR), 3D memory, stacked memory such as HBM/HBM2, and spin Ram,PSRAM.

As used herein, the terms “microprocessor” and “processor” or “digitalprocessor” are meant generally to include all types of digitalprocessing devices including, without limitation, digital signalprocessors (DSPs), reduced instruction set computers (RISC),general-purpose (CISC) processors, microprocessors, gate arrays (e.g.,FPGAs), PLDs, reconfigurable computer fabrics (RCFs), array processors,secure microprocessors, and application-specific integrated circuits(ASICs). Such digital processors may be contained on a single unitary ICdie, or distributed across multiple components.

As used herein, the terms “MSO” or “multiple systems operator” refer toa cable, satellite, or terrestrial network provider havinginfrastructure required to deliver services including programming anddata over those mediums.

As used herein, the terms “MNO” or “mobile network operator” refer to acellular, satellite phone, WMAN (e.g., 802.16), or other network serviceprovider having infrastructure required to deliver services includingwithout limitation voice and data over those mediums.

As used herein, the terms “network” and “bearer network” refer generallyto any type of telecommunications or data network including, withoutlimitation, hybrid fiber coax (HFC) networks, satellite networks, telconetworks, and data networks (including MANs, WANs, LANs, WLANs,internets, and intranets). Such networks or portions thereof may utilizeany one or more different topologies (e.g., ring, bus, star, loop,etc.), transmission media (e.g., wired/RF cable, RF wireless, millimeterwave, optical, etc.) and/or communications or networking protocols(e.g., SONET, DOCSIS, IEEE Std. 802.3, ATM, X.25, Frame Relay, 3GPP,3GPP2, LTE/LTE-A/LTE-U/LTE-LAA, 5G NR, WAP, SIP, UDP, FTP, RTP/RTCP,H.323, etc.).

As used herein, the term “network interface” refers to any signal ordata interface with a component or network including, withoutlimitation, those of the FireWire (e.g., FW400, FW800, etc.), USB (e.g.,USB 2.0, 3.0. OTG), Ethernet (e.g., 10/100, 10/100/1000 (GigabitEthernet), 10-Gig-E, etc.), MoCA, Coaxsys (e.g., TVnet™), radiofrequency tuner (e.g., in-band or 00B, cable modem, etc.),LTE/LTE-A/LTE-U/LTE-LAA, Wi-Fi (802.11), WiMAX (802.16), Z-wave, PAN(e.g., 802.15), or power line carrier (PLC) families.

As used herein the terms “5G” and “New Radio (NR)” refer withoutlimitation to apparatus, methods or systems compliant with 3GPP Release15, and any modifications, subsequent Releases, or amendments orsupplements thereto which are directed to New Radio technology, whetherlicensed or unlicensed.

As used herein, the term “QAM” refers to modulation schemes used forsending signals over e.g., cable or other networks. Such modulationscheme might use any constellation level (e.g. 16-QAM, 64-QAM, 256-QAM,etc.) depending on details of a network. A QAM may also refer to aphysical channel modulated according to the schemes.

As used herein, the term “quasi-licensed” refers without limitation tospectrum which is at least temporarily granted, shared, or allocated foruse on a dynamic or variable basis, whether such spectrum is unlicensed,shared, licensed, or otherwise. Examples of quasi-licensed spectruminclude without limitation CBRS, DSA, GOGEU TVWS (TV White Space), andLSA (Licensed Shared Access) spectrum.

As used herein, the term “SAE (Spectrum Allocation Entity)” referswithout limitation to one or more entities or processes which are taskedwith or function to allocate quasi-licensed spectrum to users. Examplesof SAEs include SAS (CBRS). PMSE management entities, and LSAControllers or Repositories.

As used herein, the term “SAS (Spectrum Access System)” refers withoutlimitation to one or more SAS entities which may be compliant with FCCPart 96 rules and certified for such purpose, including (i) Federal SAS(FSAS), (ii) Commercial SAS (e.g., those operated by private companiesor entities), and (iii) other forms of SAS.

As used herein, the term “server” refers to any computerized component,system or entity regardless of form which is adapted to provide data,files, applications, content, or other services to one or more otherdevices or entities on a computer network.

As used herein, the term “shared access” refers without limitation to(i) coordinated, licensed sharing such as e.g., traditional fixed linkcoordination in 70/80/90 GHz and the U.S. FCC's current rulemaking onpotential database-coordinated sharing by fixed point-to-multipointdeployments in the C-band (3.7-4.2 GHz); (ii) opportunistic, unlicenseduse of unused spectrum by frequency and location such as TV White Spaceand the U.S. FCC's proposal to authorize unlicensed sharing in theuplink C-band and other bands between 5925 and 7125 MHz; (iii) two-tierLicensed Shared Access (LSA) based on geographic areas and databaseassist such as e.g., within 3GPP LTE band 40 based on multi-year sharingcontracts with tier-one incumbents; and (iv) three-tier shared access(including quasi-licensed uses) such as CBRS, and other bands such ase.g., Bands 12-17 and 71.

As used herein, the term “storage” refers to without limitation computerhard drives, DVR device, memory, RAID devices or arrays, optical media(e.g., CD-ROMs, Laserdiscs, Blu-Ray, etc.), or any other devices ormedia capable of storing content or other information.

As used herein, the term “users” may include without limitation endusers (e.g., individuals, whether subscribers of the MSO network, theMNO network, or other), the receiving and distribution equipment orinfrastructure such as a CPE/FWA or CBSD, venue operators, third partyservice providers, or even entities within the MSO itself (e.g., aparticular department, system or processing entity).

As used herein, the term “Wi-Fi” refers to, without limitation and asapplicable, any of the variants of IEEE Std. 802.11 or related standardsincluding 802.11 a/b/g/n/s/v/ac/ad/ax/ay/ba/be or 802.11-2012/2013,802.11-2016, as well as Wi-Fi Direct (including inter alia, the “Wi-FiPeer-to-Peer (P2P) Specification”, incorporated herein by reference inits entirety).

As used herein, the term “wireless” means any wireless signal, data,communication, or other interface including without limitation Wi-Fi,Bluetooth/BLE, 3G (3GPP/3GPP2), HSDPA/HSUPA, TDMA, CBRS, CDMA (e.g.,IS-95A, WCDMA, etc.), FHSS, DSSS, GSM, PAN/802.15, WiMAX (802.16),802.20, Zigbee®, Z-wave, narrowband/FDMA, OFDM, PCS/DCS,LTE/LTE-A/LTE-U/LTE-LAA, 5G NR, LoRa, IoT-NB, SigFox, analog cellular,CDPD, satellite systems, millimeter wave or microwave systems, acoustic,and infrared (i.e., IrDA).

As used herein, the term wireline includes electrical and opticaltransmission media such as, without limitation, coaxial cable, CAT-5/6cable, and optical fiber. As used herein, the term “xNB” refers to any3GPP-compliant node including without limitation eNBs (eUTRAN) and gNBs(5G NR).

Overview

In one exemplary aspect, the present disclosure provides methods andapparatus for enhancing bandwidth/resource scheduling with respect tobase stations (e.g., xNB's or other types of small cells) that arebackhauled by wireline networks such as DOCSIS cable networks. In oneembodiment, enhanced communication between the base station and itsbackhaul network including the wireline modem components thereof such asthe CMTS enable the backhaul network to better allocate resources on thebackhaul (including on a base station/strand-specific basis) in effectproviding a higher layer view or abstraction for resource consumptionacross a number of different strands collectively.

In one variant, an enhanced CMTS (CMTSe) is disclosed which hasprocesses operative thereon that, inter alia, enable evaluation ofdifferent served strands of the backhaul, and modification of schedulingand prioritization for DOCSIS channels allocated cable modems on eachstrand, including those operating under incipient DOCSIS networktechnologies such as DOCSIS 3.1 and 4.0. In one embodiment, a priorityscore or schedule factor is calculated for each of the evaluatedstrands; this priority score/schedule factor is used to determinerelative scheduling of resources via e.g., existing DOCSIS scheduling orallocation algorithms (e.g., on top of other resource allocationdetermined by the underlying protocols).

In one implementation, an enhanced xNB (xNBe) is configured to transmitdata regarding its configuration and operation (including for instancedata relating to the type of wireless technology and any specificfeatures relating thereto used by the base station, the number of“attached” user devices (and their type), and the geographic location ofthe base station) to the CMTSe, so as to enable the CMTSe to dynamicallyadapt the scheduling of time and/or frequency resources for each of thestrands served so as to most effectively allocate e.g., DS bandwidth onthe wireline backhaul.

In another implementation, a base station (or its backhauling CMe) isconfigured to dynamically issue temporary or short-duration “surge”requests to the CMTSe in order to enable a temporary boost in allocatedresources for that strand. In one variant thereof, one or moreprioritized service flows are temporarily established for use by thetarget CMe/B Se strand.

Employing the resource scheduling adaptation techniques discussed aboveprovides enhanced DL and UL capacity for the user device(s) connected tothe xNBe (as well as other devices which may be served by the CMe, suchas user PCs or WLAN APs), thereby effectively enabling addition of moreservices and customers to the network with a given CAPEX (capitalexpenditure) or existing available bandwidth.

The methods and apparatus described herein may also advantageously beextended to backhauls for base stations which operate in licensed,unlicensed or shared-access architectures, including where a givenbackhaul infrastructure includes heterogeneous types of cells (e.g., alicensed Band 71 or Band 12-17 cell) associated with one CMe, aquasi-licensed CBRS cell operating at 3.550-3.700 GHz associated withanother CMe, and a mmWave gNB operating at say 42 GHz associated with athird CMe).

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

Exemplary embodiments of the apparatus and methods of the presentdisclosure are now described in detail. While these exemplaryembodiments are described in the context of the previously mentionedbase station (e.g., 3GPP eNB or gNB), wireless access points usingunlicensed or quasi-licensed spectrum associated with e.g., a managednetwork (e.g., hybrid fiber coax (HFC) cable architecture having amultiple systems operator (MSO), digital networking capability, IPdelivery capability, and a plurality of client devices), or a mobilenetwork operator (MNO), the general principles and advantages of thedisclosure may be extended to other types of radio access technologies(“RATs”), networks and architectures that are configured to deliverdigital data (e.g., text, images, games, software applications, videoand/or audio). Such other networks or architectures may be broadband,narrowband, or otherwise, the following therefore being merely exemplaryin nature.

It will also be appreciated that while described generally in thecontext of a network providing service to a customer or consumer or enduser or subscriber (i.e., within a prescribed venue, or other type ofpremises), the present disclosure may be readily adapted to other typesof environments including, e.g., indoors, outdoors, commercial/retail,or enterprise domain (e.g., businesses), or even governmental uses, suchas those outside the proscribed “incumbent” users such as U.S. DoD andthe like. Yet other applications are possible.

Also, while certain aspects are described primarily in the context ofthe well-known Internet Protocol (described in, inter alia, InternetProtocol DARPA Internet Program Protocol Specification, IETF RCF 791(September 1981) and Deering et al., Internet Protocol, Version 6 (IPv6)Specification, IETF RFC 2460 (December 1998), each of which isincorporated herein by reference in its entirety), it will beappreciated that the present disclosure may utilize other types ofprotocols (and in fact bearer networks to

Moreover, while some aspects of the present disclosure are described indetail with respect to so-called “4G/4.5G” 3GPP Standards (akaLTE/LTE-A) and so-called 5G “New Radio” (3GPP Release 15 and TS 38.XXXSeries Standards and beyond), such aspects are generally accesstechnology “agnostic” and hence may be used across different accesstechnologies, and can be applied to, inter alia, any type of P2MP(point-to-multipoint) or MP2P (multipoint-to-point) technology,including e.g., Qualcomm Multefire.

Other features and advantages of the present disclosure will immediatelybe recognized by persons of ordinary skill in the art with reference tothe attached drawings and detailed description of exemplary embodimentsas given below.

Methodology

Various methods and embodiments thereof for enhancing resourceallocation and scheduling of a wireless device backhauled by a DOCSISnetwork according to the present disclosure are now described withrespect to FIGS. 7-9.

However, before discussing these embodiments, it is illustrative toreview in detail the operation of extant DOC SIS systems while servicinga wireless device via a base station backhauled thereby. Referring nowto FIG. 7, a prior art sequence 700 for wireless device serviceprovision is conceptually shown. At step 701, the CMTS and CM negotiatechannel configuration and service flows, such as for a DL bearer andservice flow as set forth in the exemplary DOCSIS protocols incorporatedby reference elsewhere herein.

Per steps 703 and 705, the user device (e.g., a 3GPP UE such as a mobiledevice or FWA) utilizes radio frequency spectrum within which it ispermitted to operate (whether natively by virtue of itschipset/architecture, or via a dynamic grant of spectrum), andimplements so-called “RACH” (random access channel) procedures tosynchronize with the base station (e.g., gNB or eNB, hereinafter “xNB”).Pursuant thereto, the UE also subsequently connects to the xNB toestablish a radio resource layer connected state (i.e., RRC Connected)via UL and DL shared channels and associated procedures. RACH and RRCprocedures are well known, and not described further herein.

Once connected, the UE transacts its application data over the xNB, CMand CMTS backhaul with e.g., a distant networked server process,utilizing e.g., 3GPP packet data network (PDN) infrastructure. As partof such transaction, application layer or user-plane (UP) data istransacted back and forth, such as for delivery of streaming media tothe connected UE. As such, the CMTS routes DL data packets destined forthe UE application to the CBSD via the CM using the established serviceflows.

Per step 707, the UE and the core transact data via the BS (xNB) and thebackhaul. The process of steps 701-707 is repeated across multipledifferent CM/BS strands, such as each time a UE attaches to a given basestation. These steps may occur concurrently across the different CM/BSstrands, in a staggered fashion, and may occur randomly.

Per step 709, a second UE synchronizes, connects and attaches to theBS/core, and per step 711, the first and second UE each transact dataover the wireline backhaul including the CM and CMTS. It will beappreciated that FIG. 7 is somewhat of a simplified representation ofthe actual operations and steps; for instance, data is transactedmultiple times between each UE and xNB during RACH and connection, andbetween each xNB and the core during attachment, as well as fornegotiation with the network server, etc. Per step 713 of the method700, the CM and CMTS negotiate modifications to existing service flowsas needed to support the data load from the two (or more) UEs.

As a brief aside, for DOCSIS 3.0, downstream channels employ adownstream scheduler process operative at the CMTS that manages theallocation of bandwidth across multiple 6 MHz wide channels amongcompeting service flows (a transport service that providesunidirectional transport of packets). A DS service flow may consist forexample of one or more TCP/IP connections terminating at a specific CM,and service flow traffic may be prioritized based on QoS trafficparameters associated with the flow. However, the DOCSIS 3.0 standarddoes not specify how a specific scheduling implementation shoulddifferentially treat data having different priority levels.

Under DOCSIS 3.0, the upstream channel is time division (TDM)multiplexed (or SC-FDMA), and the TDM mode uses transmission slotsreferred to as mini-slots. Permission to transmit data in a block of oneor more mini-slots must be granted by a CMTS to each CM. The CMTS grantsmini-slot ownership by periodically transmitting MAP frames on thedownstream channel. The MAP also typically identifies some mini-slots ascontention slots; for these contention slots, the CMs may bid forquantities of future resources. To minimize collisions for thecontention slots, a backoff procedure is employed. Additionally, in theevent that a CM has a backlog of upstream packets, it may also“piggyback” a request for mini-slots for the next packet at the end ofthe then-current packet.

In contrast to DOCIS 3.0, DOCSIS 3.1 DS channel bandwidth is between 24and 192 MHz, and between 6.4 and 96 MHz in the US. The DOCSIS 3.1physical layer uses wideband orthogonal frequency division multiplexing(OFDM) channels (downstream) and orthogonal frequency division multipleaccess (OFDMA) channels (upstream). Due to the use of many subcarriersin an upstream channel, multiple CMs on the same upstream channel cansend data packets to the CMTS simultaneously on different subcarriers.This approach enables a very large data bandwidth through the use ofonly a single channel. Additionally, at the MAC layer, DOCSIS 3.1continues to support channel bonding. This feature now allows thebonding of OFDM/OFDMA, as well as mixed bonding of legacy single-carrierchannels and the OFDM/OFDMA channels (i.e., effectively treating anOFDM/OFDMA channel as a single-carrier channel). DOCSIS 3.1 alsorequires AQM (Active Queue Management) to reduce the buffering latencyin CM and CMTS.

In addition to the “best efforts” service previously described, otherservices may be used for traffic service flow management (depending onthe version of DOCSIS). For example, Non-real-time polling service(NRTPS) can be used for upstream service flows.

In this service, the CMTS scheduler sends unicast polls to individualCMs on a fixed interval, in order to determine whether data is queuedfor transmission on a particular service flow. If so, the CMTS schedulerprovides a transmission grant for the service flow. Associated QoSparameters for NRTPS may include Traffic priority, Request TransmissionPolicy, Maximum Sustained Traffic Rate, Maximum Traffic Burst, MinimumReserved Traffic Rate, Assumed Minimum Reserved-Traffic-Rate PacketSize, and Nominal Polling Interval.

Additionally, the Real-time polling service (RTPS) may be used forupstream service flows. RTPS is generally analogous to NRTPS, exceptthat the fixed polling interval is contracted. In RTPS, requestopportunities that meet the service flows' real-time needs can beselected, and the cable modem may specify the size of the desired grant.QoS parameters for RTPS may include Request Transmission Policy, MaximumSustained Traffic Rate, Maximum Traffic Burst, Minimum Reserved TrafficRate, Assumed Minimum Reserved-Traffic-Rate Packet Size, Nominal PollingInterval, and Tolerated Poll Jitter.

Under the Unsolicited grant service (UGS), upstream service flowsreceive a fixed-size grant at fixed intervals without additional pollingor interaction. Thus, UGS eliminates much of the overhead associatedwith the polling flow types described above. QoS parameters may includeRequest Transmission Policy, Unsolicited Grant Size, Grants perInterval, Nominal Grant Interval, and Tolerated Grant Jitter.

Unsolicited grant service with activity detection (UGS-AD) is hybrid ofthe UGS and RTPS scheduling types. When there is activity, the CMTSsends unsolicited fixed grants at fixed intervals to the CM(s).Conversely, when there is no activity, the CMTS sends unicast pollrequests to the CM(s) so as to conserve bandwidth. QoS parameters forUGS-AD may include Request Transmission Policy, Nominal PollingInterval, Tolerated Poll Jitter, Unsolicited Grant Size, Grants perInterval, Nominal Grant Interval, and Tolerated Grant Jitter.

For downstream service flows, a similar set of QoS parameters that areassociated with the best-effort scheduling type on upstream serviceflows is utilized. QoS parameters for the DS SFs may include TrafficPriority, Maximum Sustained Traffic Rate, Maximum Traffic Burst, MinimumReserved Traffic Rate, Assumed Minimum Reserved-Traffic-Rate PacketSize, and Maximum Latency.

However, despite the foregoing existing mechanisms for service flowcreation and management, there is no cognizance by the DOCSIS systemscheduler of (i) the presence of wireless base stations behind each ofthe CMs, or (ii) each of the different CM/BS strands collectively (otherthan by the underlying DOCSIS service flow protocols described above).Each strand is in effect treated in isolation and allocated resourcesaccording to the aforementioned DOCSIS protocols. Stated differently,optimizations which might occur or be available to the scheduler byvirtue of knowledge of the type and usage of equipment associated witheach of the respective CMs are not available under existing protocols,even with all of the control “granularity” discussed above, since theCMTS has no visibility beyond each CM.

With the foregoing as a backdrop, the exemplary methods of providingenhanced communication and resource scheduling according to the presentdisclosure are now described with respect to FIG. 8.

At step 801 of the method 800, the enhanced CMTS (CMTSe) 803 andenhanced CM (CMe) 831 (see FIG. 8) connect and negotiate channelconfiguration and service flows, such as for a DL bearer and serviceflows as set forth in the exemplary DOCSIS protocols described above andincorporated by reference herein. As described subsequently herein, suchnegotiation may also include the CMTSe establishing one or moredesignated/dedicated “base station” service flows for transacting datadestined for, or transmitted by, the xNBe.

Per step 803, the base station (e.g., xNBe) connects to the CMe (suchconnection which may be pre-existing, such as by virtue of e.g., IEEEStd. 802.3 or similar protocols previously executed between the MACs ofthe devices). This connection enables two-way transaction of databetween the devices. The xNBe also communicates configuration and usedata to the CMe. This data may include for instance data indicative of(i) the xNBe configuration in terms of supported technology types; (ii)the current geographic location of the xNBe (which will generally bewithin a prescribed proximity of the CMe, to the extent that thelocation of the latter is known, such as via a premises serviceaddress); and (iii) the number of connected/attached UE for the basestation.

For example, data relating to the XNBe technology type may be general(e.g., highest technology capable of being supported, such as 4G or 5GNR, Release 8-13 or Release 15-17, etc.) or highly granular, such asregarding specific features of each technology (e.g., whether the xNBesupports multiple diversity channels, SM (spatial multiplexing, andhence enhanced data throughput), or whether Dynamic Spectrum Sharing orDSS (e.g., 4G and 5G “coexistence” modes where one or more carrier areshared) are supported/enabled). This data enables the CMTSe to, in oneembodiment, assign a score or weight to that aspect of the associatedCMe regarding expected peak bandwidth consumption by the xNBe. Forexample, a 5G NR gNB device with 8-MIMO antenna and SM capabilityenables may consume, at maximal load, many times the bandwidth of afirst-generation LTE (4G) eNB. Similarly, with 5G NR low-latencyrequirements (1 ms roundtrip), any “congestion” encountered on thebackhaul may be more deleterious to the 5G NR device as compared to the4G device.

Another factor that can be leveraged by the CMTSe in determiningindividual strand or CMe scheduling is the type of spectrum employed bythe wireless node connected to a given CMe. For example, some types ofwireless technologies and spectrum have inherently higher (maximum) datarates associated with their air interfaces. A Release 17 5G NR mmWavesystem operating at e.g., 40 GHz has many times the data rate capacityof e.g., a 4G-based Band 71 interface operating at roughly 650 MHz.

Likewise, aside from data rate, different classes of spectrum may havedifferent attributes which may impact their backhaul demands. Forinstance, in the exemplary context of CBRS spectrum, PAL vs. GAAspectrum (see FIG. 3) have two different licensing models (with GAAbeing generally accessible or effectively unlicensed, and PAL beingrevocably licensed to a limited population of users). As such, PALspectrum is (at least currently) far less congested, and therefore canphysically sustain higher data rates due to e.g., better SINR, channelquality, availability of higher-order modulation and coding schemes(MCS), etc. From a business perspective, PAL spectrum may also beassociated with higher-tier or more preferred customers.

Accordingly, in some embodiments of the present disclosure, the CMTSescheduler logic is configured to utilize data obtained from the xNBe(s)relating to connected base station air interface technology andfrequency, as well as type or class of spectrum allocated to each xNBe.In some cases, this description may be broadly drawn; for example, ifthe xNBe is configured to operate only within the range of 600-800 MHzor 3.550-3.700 MHz, this data can be communicated as such, withoutparticular narrower definitions which may vary with time. Alternatively,if desired, the xNBe may be configured to provide narrower, moretime-variant descriptions, such as when a particular frequency or bandof frequencies (say 617-652 MHz on the Band 71 DL as shown in FIG. 6A)is contemplated for use for a period of time, or duration of aconnection with a given UE or set of UE. While the former approach hasthe benefit of simplicity and reduced “hopping” or adaptation that maybe needed by the CMTSe (described below), it also potentiallyover-allocates resources to the xNBe, thereby potentially unnecessarilyresulting in preemption of use of such resources by other CMes commonlyutilizing the wireline backhaul.

In terms of geographic location, different xNBe instances may or may notbe located in different types of operating environments as compared toother xNBe instances. For instance, an xNBe located in a high-densityurban application may have markedly different use statistics (and usecases) than say a rural installation of the same xNBe. In one suchvariant, the geographic data obtained by the CMTSe may be lat/lon orsimilar position data. This may be obtained from e.g., an indigenous GPSreceiver installed within the xNBe, or from a configuration or otherdata file maintained by the xNBe, such as one created by an MSOinstaller at time of installation. The xNBe may also be configured toobtain the data (e.g., via a higher layer process operative on the xNBe)from a network or cloud process, such as an MSO customer or subscriberdatabase. This location data, once received by the scheduler logic ofthe CMTSe, can be used to determine whether the xNBe is located within adesignated “hostpot”, low-use area, or other such region which allowsfor differentiation in terms of resource scheduling. For instance, inone variant, the CMTSe logic may access a historical or current “heatmap” indicating usage as a function of geographic location. Depending onthe level of usage for the xNBe location, the scheduler may categorizethe xNBe as e.g.., “high/medium/low” expected use category or other suchfuzzy variable, rank it on a numerical scale or using ascoring/weighting system, etc.

Other data which may be useful to the CMTSe in scheduling decisions isthe number of (then) current user devices attached to the xNBe. Forexample, in one embodiment, the xNBe is configured to operate using 3GPPprotocols, and the number of “attached” users is determined byenumerating the user devices in RRC Connected state. Users in RRC Idleor other states may also be included if desired, or added to anothercategory (e.g., “incipient” or “potential” users). By knowing the numberof active users actually connected to each xNBe, the CMTSe scheduler canmore accurately project usage of a given base station for at least thenear term. For instance, even if the base station is within a known ordesignated “hotspot” region, it may simply have few users due to simplestatistical variation, weather events, time of day/day of week, etc.These factors can also be folded into the data obtained by the CMTSedescribed above (i.e., the location lookup); the heat map or databasemay also include data which indicates e.g., historical temporalvariations or correlations, such as for time of day, day of week/year,etc. However, such variations may also be highly anecdotal anduncorrelated, such as where a (typically) very low use xNBe in a rurallocation has very high traffic on one day due to e.g., an event such asa fair, concert, etc.

Yet another factor which may be included in the CMTSe evaluation logicis the type of client or user device being served by the base station(and hence its' associated CMe and backhaul). For instance, a CBSDeserved by a wireline backhaul might operate as either a Category A orCategory B CBSD, depending on its configuration and grants from thecognizant SAS. As such, the higher transmit power may in some cases becorrelated to expected higher data loading. For instance, a Category BCBSD could be used as a wireless backhaul for multiple FWA devices 503(see FIG. 5), each of the FWA devices backhauling multiple devices suchas PCs, WLAN APs, and even UEs at the served premises. In contrast, aCategory A CBSD might only serve a much more limited service area (andscope of possible users), and hence may at least statistically representa lower expected backhaul load on the wireline network. Even with suchclasses (e.g., Category A and B CBSDs), differentiation may be possible,such as where a Category B CBSD may have no FWA client devices (onlye.g., mobile smartphone UEs), and hence may be categorized in a lowerputative backhaul tier based thereon.

Per step 803, the CMe transmits the received data to the CMTSe usinge.g., an established upstream bearer. It will be appreciated thatvarious different schemes for such transmission are contemplated,including e.g., (i) a “pass through” such as where the data packetscontaining the above-referenced configuration and use data are addressedto a recipient port/socket or process on the CMTSe, or (ii) the datapackets are addressed to a socket/port or process on the CMe, which uponreceipt de-encapsulates them, performs any additional processingrequired, and then re-encapsulates them and addresses them fortransmission to the target CMTSe process. For example, in some cases,the CMe may be configured to add further data to that received from thexNBe, which may be useful to the CMTSe in performing theevaluations/analysis described subsequently herein, such as e.g., dataregarding ancillary or non-BS devices also connected to the CMe (such asWi-Fi APs, PCs, etc.), channel statistics or estimation data,prioritization or classification data (such as by adding data to the IPpacket header(s) indicating that the data is associated with a wirelessbase station or other class of device which merits inclusion inscheduler calculations performed by the CMTSe).

Per step 805, the CMTSe receives the transmitted data (whetherpassed-through or appended, as previously described) from the differentCMe devices and evaluates the configuration/use data contained thereinrelating to each particular device, as described in greater detailsubsequently herein. In one variant, the data is associated with a basestation or other unique identifier which allows the CMTSe to maintain acorrelation table (e.g., LUT) or other data structure which enables theCMTSe to determine characteristics/use versus specific base station atany given point in time. The serving/connected CMe may also beidentified therein, such that the CMTSe can, if desired, formlarger-scale relationships between individual base station-equipped“strands” served by the CMTSe (such as identification of common physicalservice groups (pSGs) or “virtual” service groups (vSGs), examples ofthe latter described in co-owned and co-pending U.S. patent applicationSer. No. 16/986,131 filed Aug. 5, 2020 and entitled “APPARATUS ANDMETHODS FOR OPTIMIZING CAPACITY IN WIRELINE CABLE NETWORKS WITH VIRTUALSERVICE GROUPS,” which is incorporated herein by reference in itsentirety).

The CMe (as opposed to the BSe) may also be used as the basis of finalscheduling decisions made by the CMTSe scheduler (step 807), such aswhere the additional connected devices associated with a given CMe areincluded in scheduling evaluations, as well as the type of CM device(e.g., whether DOCSIS 3.0 or 3.1 compliant, which affect the DS and USPHY and multiple access scheme (US) used). As described in greaterdetail below, the present disclosure explicitly contemplates embodimentsof the CMTSe scheduler which can differentiate treatment/scheduling for“strands” having DOCSIS 3.1-capable CM devices (with OFDM/OFDMA in theDS/US PHY) from DOCSIS 3.0 compliant devices (which do not utilizeOFDM).

Per step 809, the CMTSe applies the developed schedule to the various“scheduled” CMe/BSe. It will be appreciated that the pool of CMe/BSewhich the scheduler considers in its schedule development may includeonly those CMe which have BSe attached (as identified by theaforementioned BS identifier value or other designation mechanism),those within a given pSG or vSG, or a more expansive set (such as allCMe served by the CMTSe).

Lastly, per step 811, the CMTSe conducts periodic monitoring of allCMe/BSe (as applicable) within the designated scheduling pool, and theschedule generated in step 807 is modified by the CMTSe scheduleraccordingly. This monitoring may be e.g., periodic polling-based,event-driven (such as on a status change), pushed by logic on theCMe/BSe, or other approach.

FIG. 8A is a logical flow diagram illustrating one implementation of thebase station configuration data collection process (step 803) of themethod of FIG. 8. As shown, per step 821, a given CMe (“N”) connects tothe CMTSe using normal DOCSIS protocols. Per step 823, the BSe (“N”)associated with CMe N initializes, and connects to CMe N (e.g., via802.3 or other wireline MAC protocols).

Per step 825, BSe N cillects and communicates its specific configurationand use data to the CMTSe (via CMe N). As previously described,transmission may be direct or indirect.

Per step 827, BSe N monitors its own status (e.g., via one or moremanager processes thereon) and where a change occurs which requiresupdate to its previously transmitted data—such as a new UEsynchronization/connection and attachment request—the BSe (N) collectsthe (new) data and transmits it to the CMTSe via the CMe (N). Otherwise,the BSe logic enters a wait state 831.

It will be appreciated that the data may be transmitted as a completenew data set (e.g., an update to all relevant data regardless ofchange), or as a “differential” or update only of the data which has infact changed since the prior update. Again, such updates may beevent-driven, according to a prescribed schedule, “pulled” by the CMTSevia polling, or pushed to the CMTSe by the BSe based on a schedule.

FIG. 8B is a logical flow diagram illustrating one variant of theprocess of FIG. 8A (step 825 for collecting data). Specifically, asshown, the BSe N first collects configuration file data, such as thatwith “nameplate” data such as model number, serial number, MAC address,as well as installation date, installation location, number of antennasectors, steering/azimuth data, and/or other salient data of utility tothe CMTSe scheduler (step 837).

Per step 839, the BSe then collects “dynamic” data, such as number ofcurrently attached UE. This data may also be granular in terms of e.g.,UE per sector/PCI, or other attributes if desired.

Per step 841, the BSe N also collects current spectrum grant and activePCI data (such as where the BSe is a CBSD that has received a PAL or GAAgrant for a given PCI from a network SAE such as a SAS).

Per step 843, the BSe then aggregates the necessary portions of thecollected data (which in one variant can be dynamically specified to theparticular BSe N by e.g., the CMTSe via downstream signaling or packetsakin to MAP frames). Notably, the CMTSe may desire or request targetedor heterogeneous data/types of data from different CMe/BSe (such as tominimize upstream reporting bandwidth consumed by the CMe in theaggregate, by obtaining only needed data), or use a “broadcast” approachwhere the requested data is homogeneous (and potentially over-inclusive,yet which is less overhead intensive on the CMTSe).

Lastly, per step 845, the BSe transmits the collected data to the CMTSe,such as via transmission of Layer 2 or 3 packets marked in their headeras originating from a base station to a target port/socket of the CMTSe.

FIGS. 8C-8F are logical flow diagrams illustrating one implementation ofthe base station and CMe evaluation process (step 805) of FIG. 8.

In FIG. 8C, the evaluation process 805 shown begins with a counter (N)set to an initialization value (e.g., 1) per step 846. Next, for Bse N,its location is determined per step 847, and a database is accessed todetermine average/historical activity of that BSe where such data isavailable per step 849. For example, as discussed elsewhere herein, aheat map or similar data structure may be algorithmically accessed basedon the determined BSe location, such as by the CMTSe receiving thelocation data (or by the BSe itself as in other embodiments describedherein). Based on the determined activity level (which e.g., may be anaverage over a period of time), a score is assigned for that BSe perstep 851. For instance, in one implementation, the score comprises avalue from 1 to 10, or a fraction/percentage (e.g., 0.70 out of possible1.0), with higher scores indicating higher (putative) activity levels.

Per step 852, if the last BSe in the pool under consideration by theCMTSe scheduler has not been evaluated for location/activity, then perstep 853 the counter (N) is incremented and the data of the next basestation evaluated. Otherwise, the method proceeds to step 805 b in FIG.8D.

As shown in steps 855-863 of FIG. 8D, logic similar to that of FIG. 8Cis applied to the BSe data, yet this time to the technology type datavia access of the configuration file associated with the BSe (step 857).Based on the configuration file data, a database is accessed in step 859to determine particular features of the e.g., generic technology type,such as for example presence of spatial multiplexing capability, maximumdata rates, modulation orders/MCS schemes, and other data which mayassist the scheduler in characterizing or rating the technology type.Note that this data may also simply be provided by the configurationfile (e.g., as extracted by the BSe when configuring the data fortransmission to the CMTSe), although this may consume more bandwidth andoverhead then merely “indexing” the technology type so that the CMTSecan access aa back-end database for the detailed data.

Again, as in FIG. 8C, the technology data is used to generate a scorefor the BSe being evaluated, such as using the aforementioned 1-10numerical or fractional scale, with higher values indicating highmaximum data rates of the technology. For example, a BSe that is 5G NRRelease 17 capable and operates with mmWave frequencies and SM mayreceive a score of “10”, whereas a legacy 4G eNB operating at 1.8 GHzmay receive a much lower score, such as “4.”

When the last BSe of the pool has been evaluated, the method proceeds tostep 805 c in FIG. 8E.

As shown in steps 865-873 of FIG. 8E, logic similar to that of FIGS. 8Cand 8D is applied to the BSe data, yet this time to the user activitylevel and diversity, via access of attached UE data maintained withinthe BSe (step 867). For instance, in one variant, the BSe maintains alist of actively attached (e.g., RRC Connected) UE based on a uniqueidentifier such as an IMEI or MAC address or similar data. Based on theaccessed data, a database is accessed in step 869 to determineparticular features of the UE, such as for example maximum technologycapability (e.g., 4G or 5G NR), spatial multiplexing capability, devicetype (e.g., mobile device, fixed device such as FWA, or other),available modulation orders/MCS schemes, and other data which may assistthe scheduler in characterizing or rating the attached UE(s).

Again, as in FIGS. 8C and 8D, the UE number and characterizing data isused to generate a score or weight for the BSe being evaluated, such asusing the aforementioned 1-10 numerical or fractional scale, with highervalues indicating high loading of the BSe. Multiple UE connected andeach comprising a 5G NR-capable FWA (which itself is backhaul for yetadditional downstream devices) might be scored a “10” of 10, while alesser number of 4G only mobile UE such as smartphones might be given alesser score. As such, the score assigned per step 871 is in oneembodiment a composite score, istelf which may be weighted based onattributes. For example, the number of UE attached may be thepredominant feature which determines bandwidth consumption, and as suchthat aspect may be weighted as e.g., “0.7”, while the UEtechnology/device type may be weighted “0.3” such that the total weightcalculated per step 871 is 1.0, such as in Eqn. (1):

W _(UE)=[(W ₁ *S ₁)+(W ₂ *S ₂)]/(W ₁ +W ₂)   Eqn. (1)

where;

-   -   W_(UE)=effective UE score    -   W_(n)=weight of factor n    -   S_(n)=score of factor n        It will be noted that the presence of both BSe technology data        and connected UE data in the illustrated embodiment        advantageously provides for enhanced accuracy in terms of        modeling demand for a BSe. Specifically, while a given BSe may        have a certain maximum capability (e.g., on a per-UE basis),        such as 5G NR Release 17 mmWave capability with a high degree of        SM, that does not mean the BSe is (or will) actually use that        capability. If all UE attached to the BSe are currently        4G-enabled only, then even with several UE, the aggregate        bandwidth consumed by the BSe on the backhaul will be far less        than the maximum that might be determined using steps 855-861 of        FIG. 8D alone, and as such using both metrics allows the CMSTe        scheduler to avoid “over-allocations” of resources to such BSe.        Conversely, in the case where a 5G NR-capable UE is attached to        a 4G-only legacy BSe, the BSe in that instance acts as the        bottleneck, and the higher-capability UE(s) cannot “force” more        capacity on the BSe or its backhaul. As such, the BSe limitation        will act as a limit for anything downstream.

When the last BSe of the pool has been evaluated, the method proceeds tostep 805 d in FIG. 8F. As shown in steps 875-883 of FIG. 8F, logicsimilar to that of FIGS. 8C-8E is applied, yet this time to otherancillary equipment which may be connected to and backhauled by the sameCMe as the BSe. In the typical CMe configuration, a number of backed orDS ports (such as RJ-45 jacks supporting 802.3-based GbE or similarcommunication between devices) are used to enable the CMe to providebackaul and switching functionality for a premises. For instance, a CMe(see FIG. 15) may support the BSe, as well as a user's PC, a WLANrouter, an IoT gateway, or other such devices, all of which arebackhauled by the MSO HFC network. As such, underestimation of CMebandwidth requirements may result if only the BSe is evaluated aspreviously described. Hence, in FIG. 8F, the CMe logic and configurationdata is accessed (whether indigenously by its own residentsoftware/firmware processes, or by polling or other request mechanism ofthe CMTSe) in order to determine (i) the configuration of the CMe itself(e.g., whether DOCSIS 3.0 or 3.1 compatible), and (ii) the configurationand/or identity of devices connected to the CMe as their backhaul (step877). It will be recognized that as of the date of this writing, bothDOCSIS 3.0 and 3.1 enabled CMs are prevalent within a typical MSOnetwork; however, as time goes on and upgrades proceed, DOCSIS 3.0devices will slowly be retired in favor of 3.1 devices (and even 4.0 andDOCSIS ES devices). In that each of the exemplary 3.0 and 3.1technologies utilize different PHY and other features (including serviceflow and QoS features) as well as channel bonding capabilities, theirrespective scheduling by the scheduler is on one embodiment treatedheterogeneously based on this differentiation (as well as the other datarelating to the connected devices and base stations served by each givenstrand).

Based on the accessed data, a connected device “profile” is constructed(such as via database access by the CMTSe) in step 879 to determineparticular characterization of the other loads on the given CMe. Forexample, a WLAN MAC address reported to the CMTSe by the CMe may be usedby the CMTSe logic to assign a score or weight for ancillary or otherconnected devices, and weight this result akin to the processesdescribed above for the BSe. In another approach, an “iPerf” or similarsoftware-based data throughput tool can be used for such purposes.

Again, as in FIGS. 8C-8E, the profile/characterizing data is used togenerate a score or weight for the CMe being evaluated, such as usingthe aforementioned 1-10 numerical or fractional scale, with highervalues indicating high loading of the CMe by one or more ancillary dataconsumers. A WLAN AP (which itself is backhaul for yet additionaldownstream devices) might prompt a scored a “10” of 10, while a lesserdevice such as a PC might be given a lesser score. As in priorembodiments, the score assigned per step 881 is in one embodiment acomposite score, itself which may be weighted based on attributes. Forexample, the presence of one or more WLAN APs may be a determinativefactor which determines bandwidth consumption, and as such that aspectmay be weighted as e.g., “0.7”, while the presence of other devices suchas PCs, home security devices, IoT gateways, etc. may be weighted inprogressively lower values. An IoT gateway, even when servicing multipleIoT “clients” such as via a BLE or PAN interface, has comparatively verylow bandwidth consumption as compared to a PC, which generally will haveless consumption than a WLAN AP.

FIG. 8G is a logical flow diagram illustrating one implementation of theCMe schedule determination process (step 807) of FIG. 8. As shown, themethod 807 includes first initializing a counter (e.g., “N”) per step884. Next, per step 885, the assigned location score for BSe N (fromFIG. 8C above) is obtained, such as from a memory location of the CMTSe(or relevant BSe). Similarly, in steps 886, 887, and 888, the respectivetechnology type score, UE activity score, UE type score are obtained forBSe N, and the ancillary connected equipment score obtained for CMe N(i.e., the CMe backhauling BSe N). The method 807 proceeds through all NBSe/CMe per steps 890 and 891 until such score data has been obtainedfor all devices in the pool being scheduled by the CMTSe.

Per step 892, the CMTSe then utilizes the collected data to calculate anaggregate score for each CMe. It is noted that since the CMTSe isestablishing service flows and scheduling resources for each CMe in thepool (as opposed to the BSe or other equipment behind the CMe), thiscalculation is performed on a per-CMe basis in the illustratedembodiment for simplicity.

In one embodiment, a weighted score is calculated for each CMe, such asin Eqn. (2):

W _(CME)=[(W ₁ *S ₁)+(W ₂ *S)+(W ₃ *S ₃)+(W ₄ *S ₄)+(W₅ *S ₅)+(W ₆ *S₆)]/(W₁ +W ₂ +W ₃ +W ₄ +W ₅ +W ₆)   Eqn. (2)

where;

W_(CME)=effective CMe score

W_(n)=weight of factor n

S_(n)=score of factor n

In one variant, the weights (Wn) in Eqn. (2) above are generated apriori based on modeling performed by the network operator (e.g., MSO)based on historical data. For instance, data can be gathered by the MSOduring operation on service flow allocations performed by the CMTS/CMTSefor known base station installations and other types of CMeconfigurations (e.g., with attached WLAN, PC, etc. as described above),and weights assigned based on e.g., statistical averages or other suchquantities. Alternatively (or concurrently), a deep learning (DL) ormachine-learning based approach can be employed, such as where data onCMTSe allocations for various types of premises installations is fed toa DLA (deep learning accelerator) function, including one operated by athird party cloud service provider. The DL approach allows for adaptiveweight modification over time; as the DL algorithms are fed new dataduring operation, the weights Wn can be changed to reflect thethen-prevailing best model of the pool of modeled network consumers(CMe).

Such weights may vary significantly as a function of time or otherfactors, such as time of day, day of week/year, occurrence of events(e.g., pandemics which force workers to work at home and henceostensibly consume more bandwidth of certain types, or naturaldisasters, etc.), network component failure or maintenance, etc. Assuch, the CMTSe in one embodiment uses a series of operational profileswhich may be changed dynamically for allocation based on such factors(e.g., a “weekday” profile, “holiday” profile). It will be appreciated,however, so as to avoid the system “hunting” and to enable greaterstability, changes in the resource allocations based on changes in scoremay be throttled or limited to a certain minimum interval (e.g., onceper minute, hourly, daily, etc.).

Lastly, per step 893, the determined scores are used to scheduleresources for the various CMe in the pool. In one embodiment, the CMTSescheduler uses the expression shown in Eqn. (3) below in order todetermine scheduling (e.g.,, an order of priority) for the variousCMe/strands being managed:

CMTSe Schedule Factor (SF)=(Weight Factor for Traffic Load)*(WeightFactor for Base Station Location)*(Weight Factor for Base StationTechnology Type)*(Weight Factor for User Devices Served by BaseStation)*(Weight Factor for User Devices Served by CMe)*(Number ofAssigned Time Slots)   Eqn. (3)

Each of the weight factors for each different assessed parameter in Eqn.(3) above may be dimensionless factors ranging from 1-10, while thenumber of time slots may also be a dimensionless value (N), therebygenerating an overall dimensionless Scheduler Factor (SF) for eachCMe/strand (or for each BSe where only that assessment is desired). Inone model, each CMe/BSe being scheduled is assigned a same number oftime slots, but with prioritization of service based on its generatedscore (e.g., a CMe serving base station with mmWave 5G capability andmultiple UE attached will be prioritized over another lessresource-intensive CMe/BSe strand due to its higher CMTSe SchedulerFactor from Eqn. (3) above). In this case, the number of time slots maybe determined by the extant DOCSIS scheduler, with the disclosedscheduler logic herein “overlaid” in order to prioritize resourceutilization for each particular CMe relative to the others based on theScheduler Factor. Stated differently, resource allocation, andprioritization of use of those allocated resources, may in oneembodiment be determined by two different processes (e.g., the existingDOCSIS scheduler and inventive scheduler disclosed herein,respectively). As a simple example, resources may be allocated to threedifferent CMe equally, yet with a first CMe having head-of-the-lineprivileges for utilizing its allocated resources, and a second CMealways second-in-line privileges.

For instance, in one variant, data packets associated with streams ofhigher prioritized CMe/BSe may be queued and transmitted before those ofother lower-ranked CMe/BSe. Such prioritization may also be applied in amore “fair” manner in cases of contention, however, so as to avoid e.g.,one highly prioritized CMe/BSe starving others of resources ormonopolizing bandwidth. For example, allocated resources may only beconsumed up to a given limit or threshold, after which other lowerpriority users will be serviced in order of descending priority fortheir allocated resources.

In other embodiments, the resources allocated to each CMe/BSe aredifferent, proportionate (or at least related) to their score In onesuch embodiment, the CMTSe scheduler merely allocates resources relativeto the score for each CMe, using a lowest (scored) CMe as a baseline asshown in the simplified example of Table 1 (a pool of 5 CMe only):

TABLE 1 CMe Score Resource Allocation 1 10 10X  2 6 6X 3 7 7X 4 1 X 5 88XFor instance, the smallest allocable increment of resources may be usedto baseline what other CMe are allocated relative thereto.Alternatively, if the total resource allocation is known (e.g., a knownvalue of Mbps based on actual or estimated total CMTSe throughput), thenthe resources may be allocated as percentages of the available total atany given time, as shown in Table 2:

TABLE 2 CMe Score Resource Allocation 1 10 31.25% 2 6 18.75% 3 7 21.88%4 1 3.13% 5 8 25.00%

In terms of actual resources allocated by the CMTSe scheduler, a varietyof different approaches may also be used. In some embodiments, thescheduler creates a schedule or allocation of available resources whichfunctions as an overlay (i.e., at a higher layer of abstraction) thanextant CMTS DOCSIS scheduler routines as previously described. Stateddifferently, the particular mechanics of allocating resources (whethertime slots in the TDM uplink of a TDMA DOCSIS 3.0 interface, or OFDMtime-frequency resources for the downlink of a DOCSIS 3.1 system, andthe various service flow management techniques described previouslyherein such as RTPS) are left to the existing DOCSIS protocols for theparticular installation; however, they are guided or governed by inputsfrom the CMTSe scheduler process. For instance, in one variant, a timeslot schedule is developed by the scheduler which allocates resourcesaccording to an allocation schedule, with the number of slots assignedto each CMe (e.g., in the DS) is “proportional” to its score, such asusing the schemes of Table 1 or 2 above. Likewise, time-frequencyresource blocks (RBs) may be used as the basis of the scheduler inOFDM-based embodiments such as the DL or UL in DOCSIS 3.1 systemsdescribed above. For instance, DOCSIS 3.1 uses an OFDM data transmissionscheme, and each OFDM subcarrier/channel is between 20 KHz and 50 KHz.Hence, one time-frequency resource may be comprised of an OFDMsubcarrier may be e.g., 20 KHz in the frequency domain, and 0.05 msec.in the time domain. By combining multiple such OFDM subcarriers, a CMTSenode can send a high amount of data in downstream. Accordingly, in onemodel, a first number (n) of OFDM subcarriers are assigned to individualCMe, and additional 20 KHz carriers can be combined consistent with the0.05 msec. time duration of those subcarriers already assigned.Moreover, each OFDM subcarrier can carry a different amount of datasymbols depending on the modulation scheme used (64 QAM, 128 QAM, 256QAM, 512 QAM, 1024 QAM, 2048 QAM, 4096 QAM), which may vary. Hence,“prioritization” by the inventive scheduler in a DOCSIS 3.1 context mayinclude prioritizing the highest scoring CMe(s) with subcarrierallocations (and any channel bonding available) first, followed byallocations to lower scoring CMe as available.

Myriad other approaches to resource allocation may be used consistentwith the present disclosure, the foregoing being only a few examples.

FIG. 9 is a logical flow diagram illustrating another embodiment of ageneralized method for wireline bandwidth allocation and scheduling,wherein individual CMe perform collection, aggregation and evaluation ofdata.

As shown in FIG. 9, the method 900 includes first negotiating US/DSchannels and service flows between the CMTSe and various CMe per step901, such as according to existing DOCSIS protocols previouslydescribed.

Per step 903, each BSe within the monitored pool reports itsconfiguration and use data to its corresponding CMe, such as via aninterposed Layer 2/3 communication protocol (e.g., MAC to MAC via 802.3protocols).

Per step 905, each CMe evaluates the configuration and use data from itsrespective BSe, including generation of scoring data based thereon.

Per step 907, the CMe then also identifies other attached equipment(e.g., PC or WLAN APs) that is using the CMe as a backhaul. Thisdetection may be accomplished based on similar 802.3 protocols and MACcommunication between the devices, or other approaches such as portactivity. Similar to the scoring for the BSe data, the CMe may alsoscore the various attached non-B Se devices using e.g., a weightedalgorithm scheme similar to that described above.

Per step 909, the CMe logic then utilizes the processed BSe and attachedequipment data (e.g., scores) to generate a compsite or aggregate scorefor the CMe. This score reflects the total estimated (and to some degreeactual) bandwidth consumption associated with the CMe duringthen-current operation.

Per step 913, the aggregate score data is then sent to the CMTSescheduler process, wherein the CMTSe uses this data (and correspondingdata from other CMe within the scheduled pool of devices) to generateand implement scheduling of the type described above (step 915).

It will be recognized that while the methodology of FIG. 9 requiresincreased processing logic on each CMe (i.e., to acquire the relevantdata, and generate scores), it also may significantly reducesignaling/overhead between the CMe devices and the CMTSe that otherwisewould be necessary using e.g., the approach of FIGS. 8-8G. In effect,each CMe acts a distributed evaluator for its own connected BSe andother equipment. In one variant, each CMe in the pool is configured witheffectively identical or standardized scoring algorithms and logicincluding weights, such that any output (e.g., scores) can be utilizedby the CMTSe scheduler process on an “apples to apples” basis. However,the present disclosure also contemplates that application-specificscoring/weighting algorithms may also be utilized, including thoseconfigured for specific types of connected BSe or other equipment beingbackhauled by each CMe.

Additionally, depending on the technology of the backhaul interface used(e.g., DOCSIS 3.0 vs. 3.1), different scoring weights and constructs maybe applied which are more specifically adapted to the underlyingprotocol. For instance, the TDMA-based UL request/grant mechanism ofDOCSIS 3.0 may require different algorithsm for weight determination,scoring and scheduling than the OFDMA-based UL of DOCSIS 3.1 systems.

Network Architectures

FIG. 10 is a block diagram illustrating one exemplary embodiment ofnetwork configuration with enhanced backhaul scheduling functionalityaccording to the present disclosure.

As a brief aside, the so-called modular headend architecture (MHA; seee.g. CableLabs Technical Report CM-TR-MHA-V02-081209, which isincorporated herein by reference in its entirety) essentially separatesthe downstream PHY layer out of the CMTS, and move it to a separate EQAMdevice. In this architecture, the CMTS transmits data to the EQAM viathe Downstream External PHY Interface (DEPI). This architecture wasintroduced in order to reuse EQAM to modulate both the data bits as MPEGvideo bits. The upstream receiver is kept in the CMTS in the MHA.

In contrast, another architecture used in implementing headend platformsis the Converged Cable Access Platform (CCAP). In order to increaseefficiency, the CCAP integrates the EQAM and CMTS into one platform. Inaddition, in the CCAP, all the downstream traffic, including DOCSIS andvideo QAMs are transmitted in a single port. The CCAP unifies the CMTS,switching, routing, and QAM modulator in one unit, so that all data andvideo are converted in IP packets before conversion to RF signals.

The Remote PHY technology, also known as Modular Headend ArchitectureVersion 2 (MHAV2), removes the PHY from the CMTS/CCAP platform andplaces it in a separate access point that is interconnected with an IPnetwork. One common location to place the remote PHY is the optical nodethat is located at the junction of the fiber and coax cable networks.

In the MHAV2 architecture, the CCAP includes two separate components,CCAP core and the Remote PHY Device (RPD). The CCAP core contains a CMTScore for DOCSIS, and an EQAM core for video. The CMTS core contains theDOCSIS MAC, upper layer DOCSIS protocols, all signaling functions,downstream and upstream scheduling. The EQAM core processes all thevideo processing. Similarly, an RMD (generally analogous to the RPD, butcontaining the DOC SIS MAC, also colloquially referred to a s a “FlexMAC”) is also specified; see e.g., CableLabs Technical ReportCM-TR-R-MACPHY-V01-150730, which is incorporated herein by reference inits entirety.

The RPD/RMD processes all the PHY related function, such as downstreamQAM modulators, upstream QAM demodulators, upstream coders, downstreamdecoders, filtering, time and frequency synchronization, as well as thelogic to connect to the CCAP core. One motivation for using suchapproaches as RPD/RMD is the ability to obviate analog fiber componentsbetween the headend and optical nodes, and rather utilize digitaloptical PHY and interfaces thereby enhancing quality at the nodes.

Hence, it will be appreciated by one of ordinary skill given the presentdisclosure that the exemplary network architectures described below withrespect to FIGS. 10-12 may be readily adapted to any of the foregoingmodels or paradigms (e.g., MHA, MHAv2, etc.), and yet otherconfigurations are possible, those of FIGS. 10-12 being merelynon-limiting examples.

Referring again to FIG. 10, a functional block diagram illustrating afirst exemplary configuration of an HFC network architecture apparatusaccording to the present disclosure is shown, with enhanced CMTS (CMTSe)and EQAMs located at a cable system headend 1002. This embodimentleverages existing architectures which utilize a headend-based CMTS andEQAM, yet with further expansion of CMTS capabilities. Specifically, asdescribed in detail subsequently herein, the enhanced CMTSe 1003 shownincludes additional logic which supports base station service flowestablishment and resource scheduling (and subsequentadaptation/modification functions), as well as others described herein.It will be appreciated that the various aspects of the disclosure may beimplemented such that some aspects of the CMTSe 1003 is not required;i.e., a CMTSe without base station service flow designation capabilitymay be used, such as where a prioritized or dedicated service flow forthe base station(s) served by the CMTSe (and associated CMe) is notdesired or required.

As shown, the architecture 1000 of FIG. 10 includes the CMTSe 1003, aswell as switch logic that interfaces the CMTSe with one (or more) EQAMs105. Output of the EQAMs is combined with video and other signals, andthe combined (optical domain) signal transmitted downstream via opticalfiber to one or more nodes within the HFC topology (not shown in FIG.10) for ultimate delivery to CMe devices 1025 for use by premises CPE(such as e.g., BSe such as 3GPP-enabled xNBe devices 1031, Wi-Fi-enabledrouters, PCs, gateways, or other devices) within the served premises. UE139 and FWA 143 may be served by the xNBe devices at each premises asshown. For instance, in one model, the xNBe 1031 is disposed on abuilding rooftop or facade, and mobile users can access the xNBe viae.g., CBRS spectrum, or Band 71 or Band 12-17 spectrum. In anothermodel, the xNBe is a high power device which is used as a wirelessbackhaul for a number of FWA devices 143 (effectively fixed 3GPP UE thatservice e.g., residential premises). Many other service models arepossible.

In the embodiment of FIG. 10, the MSO domain is interfaced with anexternal MNO domain via the MSO backbone 151, such as where anMNO-operated EPC/5GC 1053 which also services MNO cells (cellular xNBs)and small cells 1027 is the cognizant core for the MSO domain users.

FIG. 11 is a functional block diagram illustrating a second exemplaryconfiguration of an HFC network architecture apparatus according to thepresent disclosure, with enhanced CMTS (CMTSe) 1003 co-located (at leasttopologically) with an MSO-based core 1151. In this model, the MSOdomain contains all necessary components for e.g., UE attach proceduresand packet session establishment, and any MNO based networks and theirEPC/5GC infrastructure (not shown) are considered external. In that theUE's 139 are associated with MSO subscriber premises and subscriptions,and the core infrastructure is part of this “home” network, significanteconomies can be realized, as well as enhanced resource schedulingfunctionality, since the MSO maintains control of all relevant processes(including data necessary to support CPE and UE characterization, heatmaps for different service areas, wireline service profiles or templatesof the type previously described, etc.).

In contrast, in the embodiment of FIG. 10 previously discussed, thearchitecture 1000 is divided among two or more entities, such as an MNOand an MSO. As shown, the MSO service domain extends only to the xNBeand served premises and the MSO core functions, while other functionssuch as 3GPP EPC/E-UTRAN or 5GC and NG-RAN functionality is provided byone or more MNO networks operated by MNOs with which the MSO has aservice agreement.

FIG. 12 is a block diagram illustrating yet another exemplary embodimentof network configuration with enhanced backhaul scheduling functionalityaccording to the present disclosure, wherein a network-based basebandprocessing functionality is utilized.

In this architecture 1200, the xNBe/CBSDe functionality is partitionedinto an rCBSDe (reduced-profile CBSDe) 1231 and a BBU (basebandprocessing unit) 805 as shown. The rCBSDe devices include antennae andRF front end processing (as well as packet generation and encapsulationfunctions), while the BBU 1205 is configured to perform basebandprocessing of the packetized data for two or more rCBSDes 1231 insupport of e.g., the wireless protocols used by the rCBSDe(s) 1231.

The BBU 1205 is in the illustrated embodiment disposed at a networkdistribution node of the HFC infrastructure, although it can be locatedat other points in the network as well (such as at the headend, andco-located with the CMTSe 1003).

In one implementation, the BBU 1205 operates to receive data originatedby the rCBSDe devices 1231 and transmitted over the wireline PHY betweenthe CMe and the CMTSe. For instance, in one such approach, each rCBSDe1231 includes sufficient processing to receive wireless signals from aUE or FWA (i.e., according to 3GPP protocols) such as relating tocontrol plane functions including synchronization and/or RRC connectionand attachment by a UE, and packetize the control plane data into Layer2/3 packets for transmission to the BBU 1205 via the wireline backhaul.For example, the rCBSDe can generate IP packets which can be designatedas previously described (e.g., explicitly as base station-originatedpackets, or those specifically relating to BSe configuration and use),and passed to the BBU 1205 via a prioritized service flow between theCMTSe and the CMe associated with the rCBSDe, with the CMe queuing thepackets in the appropriate service flow buffer(s) based on the detectedtype in e.g., the IP header. Likewise, in another variant, the 3GPPcontrol plane data can be encapsulated in Ethernet or MAC frames,designated or marked, and routed according to such protocols, includingto the BBU 1205.

In one variant, the BBU 1205 includes necessary modem(s) forcommunication on the wireline PHY (e.g., DOCSIS compatible modemcapability in US and DS directions), and can be a logical endpoint forthe packets generated by the rCBSDe(s) 1231. For instance, the BBU mayact effectively as a pass-through for data packets between the CMTSe andthe CMe, with the exception of packets addressed to the BBU as anendpoint (i.e., in the US direction), or for the rCBSDe or a UE attachedthereto (in the DS direction).

CMTSe Apparatus

FIG. 13 is a block diagram illustrating one exemplary embodiment ofnetwork converged headend and remote PHY device (RPD) configuration withenhanced scheduling functionality according to the present disclosure.

In the Remote PHY (R-PHY) architecture, which is a distributed accessarchitecture, the PHY layer is moved from CMTSe (headend) to the fibernodes within the HFC network. By decreasing the distance to clientdevice, the R-PHY can achieve higher bandwidth and throughput than amodular or integrated CCAP architecture, and hence it can provide higherbandwidth and throughput. It will be appreciated however that nonRPD/RMD based variants may be used as well consistent with the presentdisclosure, such as via the modular CCAP or integrated CCAParchitectures. In such architectures, the PHY and MAC layers areimplemented in the headend.

As illustrated, the architecture 1300 includes one CMTSe module 1303physically located at the headend, and one or more R-PHY modulesphysically located at fiber nodes. The CMTSe device 1303 includes aprocessor 1305, modem 1307 (which may be integrated in the CPU 1305, orimplemented as a separate processor or ASIC as shown), RF front end1319, downstream MAC 1311, upstream MAC 1313, upstream PHY 1317, RFfront end 1318, memory 1309, CPE characterization logic 1336, andservice flow & scheduling management (SFSM) logic 1337, each integratedin memory module 1309. Additionally, the exemplary embodiment 1300includes a network interface 1303 that interfaces CMTSe 1303 to connectto a data network (e.g., MSO backbone and/or other network as describedin FIGS. 10-12).

The illustrated architecture 1300 also includes a CPE database 1345,which in one embodiment is configured to store data regarding CPE whichmay be “scored” or otherwise evaluated by the CMTSe logic. For example,such CPE might include: (i) CMe, (ii) BSe associated with each CMe, (ii)UE, (iv) WLAN APs, (v) PCs, and other types of premises devices. Each ofthese devices may be uniquely identified (e.g., by MAC address, IMEI, orother such unique identifier) and associated with a given CMe (and itsserved premises), which may also utilize subscriber account data accessto maintain this information for use by the CMTSe logic. For example,when a new CMe is installed at a new service location, and a small cell(e.g., BSe) is installed, the installer may transmit this data to thesubscriber database portal of the MSO network, such that the networkmaintains all identifying and installation data for that subscriberpremises/account, which can then be made accessible (or synchronizedwith) the CMTSe CPE DB 1345.

The components of the CMTSe device 1303 shown in FIG. 13 may beindividually or partially implemented in software, firmware or hardware.

In the exemplary embodiment, the processor(s) 1305, 1307 may include oneor more of a digital signal processor, microprocessor,field-programmable gate array, GPU, or plurality of processingcomponents mounted on one or more substrates. The processor may alsocomprise an internal cache memory, and is in communication with a memorysubsystem 1309, which can comprise, e.g., SRAM, flash and/or SDRAMcomponents. The memory subsystem may implement one or more of DMA typehardware, so as to facilitate data accesses as is well known in the art.The memory subsystem of the exemplary embodiment containscomputer-executable instructions which are executable by theprocessor(s) 1305, 1307.

The downstream MAC 1311 adds overhead (e.g., MAC address, AutomaticRepeat request (ARQ)) to data, and divides the data stream into MACframes. Likewise, an US MAC 1313 is provided for data traffic sent frome.g., the CMe(s).

The SFSM logic 1337, among other functions, identifies the transmittedpackets from the xNBe 1031 (via the CMe 1025) where so implemented,reads the header fields to determine the packet type (e.g., BSassociated), and allocates any required service flows to the serving CMeif such functionality is utilized. Also, depending on the type of thereceived packet from the CMe, the CMTSe 1003 extract data from thepackets relating to xNBe configuration and use. As described previously,in one embodiment, the data identified as associated with the xNBe (suchas by IP packet header inspection) can be allocated to an xNBe-specificservice flow established between the CMTSe and CMe, although this is nota requirement of practicing the various other aspects of the invention.

In the RPD, the Edge QAM/Downstream PHY module 1315 receives the MACdata from the module 10811, adds redundancy (e.g., Forward Error ControlCoding (FEC)) to the data, and converts the data to PHY layer data andvideo signals (e.g., 16-QAM, 256-QAM). The D/A device 1316 converts thedigital received signal from module 1315, and converts it to analogsignal to be converted to RF signals by RF front end unit 1319. The A/Dmodule 1318 receives the analog baseband signals from RF front end unit1319, and converts it to digital signal. The upstream PHY module 1317converts the received base baseband signal constellation to data bits.The data bits from PHY module 1317 are divided in MAC frames by upstreamMAC module 1313, and decoded by modem IM 1307.

The RF front end 1319 includes RF circuits to operate in e.g. DOCSIS 3.1or 4.0 supported frequency spectrum (5-42 MHz upstream, 43-366 MHz VOD,SVD, broadcast channels, 367-750 MHz, 751 MHz-1.2 GHz downstream). Themodem 1307 generates the upstream and downstream PHY/MACH control anddata, timing, and synchronization signals. The CPU 1305 is the mainprocessing component in the CMTSe device 1003; it generates the signalto control other components in the CMTSe 1003 and the network (includingthe various CMe to which it is connected), fetches and stores data frommemory 1309, and generates the signals and commands for the networkinterface 1303.

Base Station Apparatus

FIG. 14 is a block diagram illustrating one exemplary embodiment ofenhances base station (e.g., xNBe) apparatus configured for provision ofenhanced wireline scheduling functions according to the presentdisclosure.

As shown, the xNBe 1031 includes, inter alia, a processor apparatus orsubsystem 1445, a program memory module 1450, mass storage 1448, one ormore network interfaces 1456, as well as one or more radio frequency(RF) devices 1431 having, inter alia, antenna(e) 1421 and one or more4G/5G radio(s).

At a high level, the xNBe maintains a 3GPP-coompliant LTE/LTE-A/5G NR“stack” (acting as a EUTRAN eNB or 5G gNB) communications with3GPP-compliant UEs (mobile devices 139), as well as any other protocolswhich may be required for use of the designated frequency bands such ase.g., CBRS GAA or PAL band, C-Band, or Band 71.

As illustrated, the xNBe device 1031 includes configuration data logic1451, and CMTSe coordination logic 1459.

The configuration data logic 1451 includes a variety of functionsincluding assembly of configuration and use data relating to the XNBefor transmission to the CMTSe 1003 via the CMe 1025 as previouslydescribed. xNBe identifier data may also be generated an processed bythe logic 1451. In this latter process, the configuration logic 1451adds a base station “identifier” or other designator in the IP packetheader that denotes the packet type and the base station identity(either generically or specifically as desired). In some embodiments,the logic 1451 may be configured to add additional marking oridentifiers to certain packets, so as to e.g., associate them with aparticular function or service flow established within the CMe.Alternatively, the logic 1451 may simply address certain packets tocertain sockets or ports within the CMe.

The CMTSe coordination logic 1459 performs CMTSe coordination functions,such as those described previously herein with respect to FIGS. 8-9. Forexample, the xNBe may be configured to receive commands from the CMTSe(via the logic 1457) and implement one or more tasks or routines whichhelp the CMTSe evaluate the xNBe (and CMe), and/or other devices, forconfiguration and usage by UE. For instance, a CMTSe may poll the BSe1031 via the coordination logic, and the BSe may reply with data inresponse to the request, such as via Layer 2/3 communications on theupstream. Similarly, the CMTSe may direct individual BSe to performother tasks or testing, such as issuing broadcast or “probe” messaging(e.g., to determine the presence of nearby but unattached UE),iPerf-based data throughput tests between the CMTSe and the BSe, changesin configuration (e.g., suppression or suspension of SM, DSS, or othermodes of operation which may consume additional bandwidth on thebackhaul, use of certain sectors, etc.), changes in modulator order orMCS, etc.).

In the exemplary embodiment, the processor 1445 may include one or moreof a digital signal processor, microprocessor, field-programmable gatearray, GPU or plurality of processing components mounted on one or moresubstrates. The processor 1405 may also comprise an internal cachememory, and is in communication with a memory subsystem 1450, which cancomprise, e.g., SRAM, flash and/or SDRAM components. The memorysubsystem may implement one or more of DMA type hardware, so as tofacilitate data accesses as is well known in the art. The memorysubsystem of the exemplary embodiment contains computer-executableinstructions which are executable by the processor. Other embodimentsmay implement such functionality within dedicated hardware, logic,and/or specialized co-processors (not shown).

The RF antenna(s) 1421 are configured to detect and transceive signalsfrom radio access technologies (RATs) in the service area or venue withwhich the xNBe 1031 is associated. For example, LTE (including, e.g.,LTE, LTE-A, LTE-U, LTE-LAA) signals may be used as the basis ofcommunication between the CBSD/xNBe 1031 and the various mobile devices(e.g., UEs 139) or FWA 143. The antenna(s) 1421 may include multiplespatially diverse individual elements in e.g., a MIMO- or MISO-typeconfiguration, such that spatial diversity of the transceived signalscan be utilized for e.g., increase in coverage area.

In the exemplary embodiment, the radio interface(s) 1431 comprise one ormore LTE/5G-based radios compliant with 3GPP. Additional unlicensed,licensed, or quasi-licensed air interfaces may also be used within theXNBe, including e.g., Wi-Fi, non-CBRS band LTE or 5G NR, or others.Moreover, the LTE radio functionality may be extended to incipient3GPP-based 5G NR protocols; e.g., at maturation of LTE deployment andwhen 5G NR-enabled handsets are fielded, such adaptation beingaccomplished by those of ordinary skill given the contents of thepresent disclosure. As a brief aside, NG-RAN or “NextGen RAN (Radio AreaNetwork)” is part of the 3GPP “5G” next generation radio system. 3GPP iscurrently specifying Release 17 NG-RAN, its components, and interactionsamong the involved nodes including so-called “gNBs” (next generationNode B's or eNBs). NG-RAN will provide very high-bandwidth, verylow-latency (e.g., on the order of 1 ms or less “round trip”) wirelesscommunication and efficiently utilize, depending on application, bothlicensed and unlicensed spectrum of the type described supra in a widevariety of deployment scenarios, including indoor “spot” use, urban“macro” (large cell) coverage, rural coverage, use in vehicles, and“smart” grids and structures. NG-RAN will also integrate with 4G/4.5Gsystems and infrastructure, and moreover new LTE entities are used(e.g., an “evolved” LTE eNB or “eLTE eNB” which supports connectivity toboth the EPC (Evolved Packet Core) and the NR “NGC” (Next GenerationCore).

The RF radios 1431 in one embodiment comprises a digitally controlled RFtuner capable of reception of signals via the RF front end (receivechain) of the RF radio(s) in the aforementioned bands, including in onevariant simultaneous reception (e.g., both CBRS and 2.300 to 2.500,bands, CBRS and 600 to 800 MHz bands, or Band 71 and Band 12/17 inanother configuration).

FIG. 14A is a block diagram illustrating one exemplary implementation ofthe base station (e.g., xNBe) of FIG. 14, illustrating different antennaand transmit/receive chains thereof.

As illustrated, the device 1460 includes baseband processor 1465, one ormore D/A 1469, one or more RF front ends 1471, one or more poweramplifiers 1473, configuration data logic 1466, and CMTSe coordinationlogic 1468. Additionally, the exemplary embodiment includes a networkinterface 1463 that interfaces the xNBe to connect to a data network viae.g., a CMe 1025.

The components of xNBe 1460 shown in FIG. 14A may be individually orpartially implemented in software, firmware or hardware. The RF frontend 1471 includes RF circuits to operate in e.g., licensed,quasi-licensed or unlicensed spectrum (e.g., Band 71, Bands 12-17, NR-U,C-Band, CBRS bands, etc.). The digital baseband signals generated by thebaseband processor 1405 are converted from digital to analog by D/As1469. The front-end modules 1413 convert the analog baseband signalsradio received from D/As 1469 to RF signals to be transmitted on theantennas. The baseband processor 1465 includes baseband signalprocessing and radio control functions, including in one variantphysical layer and Layer 2 functions such as media access control (MAC).The Power Amplifiers (PA) 1473 receives the RF signal from RF front ends1411, and amplify the power high enough to compensate for path loss inthe propagation environment.

CMe Apparatus

FIG. 15 is a block diagram illustrating one exemplary embodiment of acable modem (CMe) apparatus configured for enhanced wireline schedulingfunctions according to the present disclosure.

At high level, the CMe apparatus 1025 includes, inter alia, a processorapparatus 1505, a program memory module 1507, mass storage 1517, one ormore RF front ends 1509, 1510 for processing RF signals received andtransmitted over the coaxial “last mile” network, basebandprocessor/modem chipset 1515, as well as one or more network interfaces1503 such as, Gigabit Ethernet or other LAN/WLAN connectivity, supportof home or premises gateways, DSTBs, 3GPP small cells, etc. within thepremises, etc.

The RF modules 1509, 1510 include a heterodyne-basedtransmitter/receiver architecture generally symmetrical to thetransmitter/receiver of the enhanced CMTSe/node discussed previously;i.e., impedance matching circuitry, diplexer, synchronization circuit,tilt, etc. are used as part of the CMe RF front ends, as well as RFtuner apparatus. The RF front ends are used to convert the receivedsignal from frequency bands (366-750 MHz and 750 MHz-1.2 GHz, or to 1.8GHz for DOCSIS 4.0, or higher for so-called “Extended Spectrum DOCSIS”up to e.g., several GHz) to baseband, and the inverse for transmission.A common Fl-type connector for interface between the coaxial network andRF front end(s) is shown, although other approaches may be used as well.

Moreover, while two separate RF front ends 1510, 1509 are shown in thisembodiment, a single device covering the entirety of the desiredfrequency range may be used with generally equal success.

The network interface module 1503 may include for example GbEEthernet/WLAN/USB ports, which allows interface between the CMe moduleand premises devices such as xNBe devices 1031, WLAN routers, DSTBdevices, computers, etc., to support data interchange between the CMeand the device.

In the exemplary embodiment, the host processor (CPU) 1505 may includeone or more of a digital signal processor, microprocessor, GPU,field-programmable gate array, or plurality of processing componentsmounted on one or more substrates. The processor 1505 may also comprisean internal cache memory, and is in communication with a memorysubsystem 1507, which can comprise, e.g., SRAM, flash and/or SDRAMcomponents. The memory subsystem may implement one or more of DMA typehardware, so as to facilitate data accesses as is well known in the art.The memory subsystem of the exemplary embodiment containscomputer-executable instructions which are executable by the processor1505, including the OS and middleware 1513 (e.g., executing a Linux orother kernel).

The processor 1505 is configured to execute at least one computerprogram stored in memory 1507 (e.g., a non-transitory computer readablestorage medium); in the illustrated embodiment, such programs includelogic to implement the prioritized or dedicated service flow managementfunctionality described previously herein (including packet processinglogic 1514 for passing xNBe configuration data to the CMTSe, as well ascoordinating with CMTSe logic for implementation and utilization of anyprioritized service flows if established. Other embodiments mayimplement such functionality within dedicated hardware, logic, and/orspecialized co-processors or ASICs (not shown).

The CMe may also further be configured with queue management (QM) logic1516, which is used to monitor and maintain service flow queue levels(e.g., for UL data queues where the CMe is equipped to perform upstreamdata queue metric monitoring/analysis) such as in support of QoS orother parameter evaluations, as previously referenced herein. Forinstance, the queue logic may be used to gather data on rising bufferlevels, indicative of reduced data rates or throughputs caused by e.g.,interference with a DL or UL channel on the wireline interface.

The CMe logic may also include CMe configuration logic 1521, which isused by the CMe (and any polling or accessing process such as the CMTSe)to gather and evaluate data relating to CMe connected equipment,including that other than the BSe.

Additionally, the CMe logic may include algorithms and related logic(not shown) for performing data evaluation on the acquired or accesseddata (as well as that obtained from the BSe when so configured) in orderto implement the scoring and weighting algorithms previously described.

The CMe logic also includes a hierarchy of software layers andcommunication protocols to enable RF carrier detection, reporting andsynchronization, communication with the CMTSe 1003, interaction with PHYlayer and hardware, routing data from/to the HFC network, Layer 2/3functions, etc.

Exemplary Communications Flow

FIG. 16 is a ladder diagram illustrating communication and flow betweenUE, xNBe, CMe, and CMTSe according to one embodiment of the presentdisclosure. In the illustrated ladder diagram of FIG. 16, a UE firstattaches (e.g., synchronization and RACH) and authenticates to thenetwork core via the xNBe and CMe (and CMTSe). Packets sent from thexNBe to the CMe are marked in this embodiment, which enables the CMTSeto establish one or more new service flows dedicated to the xNBe (andits clients), including for configuration and use data to be transactedbetween the xNBe and the CMTS (i.e., between the xNBe configuration datalogic and the CMTSe scheduler logic). In one approach, the methods andapparatus for establishing prioritized UE connection described inco-owned and co-pending U.S. patent application Ser. No. 16/966,496filed August 18, 2020 and entitled “METHODS AND APPARATUS FOR WIRELESSDEVICE ATTACHMENT IN A MANAGED NETWORK ARCHITECTURE,” previouslyincorporated herein may be used consistent with the present disclosure.

Once the CMTSe and CMe negotiate the initial DL (and UL) channels andthe service flow(s) is/are established, the configuration data isrequested by the CMTSe, and responsively passed from the xNBe to theCMTSe (via the CMe), which then uses the data as necessary to evaluateand implement the scheduling and resource allocations for all CMe in thepool (only one shown for simplicity), and for necessary modifications tothe wireline interface. As shown, existing DOCSIS protocols are used toimplement the service flows and associated QoS requirements needed toimplement the higher-layer resource scheduling generated by the CMTSescheduler.

It will be recognized that while certain aspects of the disclosure aredescribed in terms of a specific sequence of steps of a method, thesedescriptions are only illustrative of the broader methods of thedisclosure, and may be modified as required by the particularapplication. Certain steps may be rendered unnecessary or optional undercertain circumstances. Additionally, certain steps or functionality maybe added to the disclosed embodiments, or the order of performance oftwo or more steps permuted. All such variations are considered to beencompassed within the disclosure disclosed and claimed herein.

While the above detailed description has shown, described, and pointedout novel features of the disclosure as applied to various embodiments,it will be understood that various omissions, substitutions, and changesin the form and details of the device or process illustrated may be madeby those skilled in the art without departing from the disclosure. Thisdescription is in no way meant to be limiting, but rather should betaken as illustrative of the general principles of the disclosure. Thescope of the disclosure should be determined with reference to theclaims.

It will be further appreciated that while certain steps and aspects ofthe various methods and apparatus described herein may be performed by ahuman being, the disclosed aspects and individual methods and apparatusare generally computerized/computer-implemented. Computerized apparatusand methods are necessary to fully implement these aspects for anynumber of reasons including, without limitation, commercial viability,practicality, and even feasibility (i.e., certain steps/processes simplycannot be performed by a human being in any viable fashion).

What is claimed is:
 1. A computerized method of operating a packetnetwork infrastructure comprising a plurality of packet receiverapparatus and at least one packet transmitter apparatus, the methodcomprising; obtaining data at respective ones of the plurality of packetreceiver apparatus from wireless equipment connected thereto, each ofthe obtained data comprising data relating to a plurality ofconfiguration aspects of the wireless equipment; and causing datarelating to the obtained data to be transmitted to the at least onepacket transmitter apparatus, the transmitted data configured to enablethe at least one transmitter apparatus to determine scheduling of radiofrequency (RF) channels utilized by the packet network infrastructurefor communication between the plurality of packet receiver apparatus andthe at least one packet transmitter apparatus.
 2. The method of claim 1,further comprising: identifying at the at least one packet transmitterapparatus, the wireless equipment connected to one of the plurality ofpacket receiver apparatus; and based at least on the identifying,causing a change in a weighting assigned to the one packet receiverapparatus, the change in the weighting affecting the scheduling.
 3. Thecomputerized method of claim 2, wherein the identifying at the at leastone packet transmitter apparatus the wireless equipment comprisesidentifying a type or configuration of a wireless base station connectedto a cable modem (CM) based at least in inspecting one or more datastructures transmitted to the CM from the wireless base station.
 4. Thecomputerized method of claim 1, wherein the packet networkinfrastructure comprises a DOCSIS (data over cable servicespecification) packet data system, the at least one packet transmitterapparatus comprises a cable modem termination system (CMTS), and theplurality of packet receiver apparatus comprises a plurality of cablemodems (CMs).
 5. The computerized method of claim 1, wherein the causingdata relating to the obtained data to be transmitted to the at least onepacket transmitter apparatus comprises causing transmission of dataindicative of the plurality of configuration aspects, the plurality ofconfiguration aspects comprising: (i) a number of attached user orclient devices; and (ii) configuration data enabling determination of ageographic location of the wireless equipment.
 6. The computerizedmethod of claim 5, wherein: the infrastructure comprises a hybrid fibercoaxial (HFC) network infrastructure; and the determination ofscheduling of radio frequency (RF) channels utilized by the packetnetwork infrastructure for communication between the plurality of packetreceiver apparatus and the at least one packet transmitter apparatuscomprises determination of a respective quantity of resources toallocate to each of the plurality of packet receiver apparatus.
 7. Thecomputerized method of claim 6, wherein the respective quantities ofresources each comprise a respective number of downlink (DL) time slots.8. The computerized method of claim 1, further comprising: obtainingsecond data at respective ones of the plurality of packet receiverapparatus relating to at least one configuration aspect of therespective packet receive apparatus; and causing data relating to theobtained second data to be transmitted to the at least one packettransmitter apparatus, the transmitted data relating to the obtainedsecond data for use in the scheduling of radio frequency (RF) channelsutilized by the packet network infrastructure.
 9. The computerizedmethod of claim 8, wherein the obtaining second data at respective onesof the plurality of packet receiver apparatus relating to at least oneconfiguration aspect of the respective packet receive apparatuscomprises obtaining data relating to one or more devices in datacommunication with the respective packet receive apparatus and requiringbackhaul by the infrastructure.
 10. Computerized network apparatus foruse in a network, comprising: at least one packet data interfaceconfigured for communication with a radio frequency transceiverapparatus; processor apparatus in data communication with the at leastone packet data interface; and storage apparatus in data communicationwith the processor apparatus, the storage apparatus comprising at leastone computer program configured to, when executed by the processorapparatus, cause the computerized network apparatus to: receive firstdata packets via the at least one packet data interface, the first datapackets comprising data relating to at least (i) a configuration of awireless access node, and (ii) operation of the wireless access node;evaluate the received first data packets to generate characterizationdata relating a plurality of operational and configuration aspects ofthe wireless access node; and cause transmission of at least a portionof the characterization data to the radio frequency transceiverapparatus, the transmission of the characterization data enablingallocation by the computerized network apparatus of resources for use by(i) at least a modem apparatus associated with the wireless access node,and (ii) a plurality of other modem apparatus in data communication withthe radio frequency transceiver apparatus.
 11. The computerized networkapparatus of claim 10, wherein: the computerized network apparatuscomprises a DOCSIS cable modem termination system (CMTS), the radiofrequency transceiver apparatus comprises a QAM (quadrature amplitudemodulation) modulator, and the modem apparatus comprises a DOCSIS cablemodem (CM) which is used to backhaul the wireless access node.
 12. Thecomputerized network apparatus of claim 11, wherein the at least onecomputer program is further configured to, when executed by theprocessor apparatus, cause the computerized network apparatus totransmit data to the radio frequency transceiver apparatus causingscheduling of respective pluralities of time slots on a plurality ofdifferent RF carriers for use by respective ones of a plurality of modemapparatus including the at least modem apparatus associated with thewireless access node, the plurality of modem apparatus having a commonoperational or configuration attribute.
 13. The computerized networkapparatus of claim 12, wherein the common operational or configurationattribute comprises membership in at least one of (i) a common physicalservice group (pSG), or (ii) a common virtual service group (vSG). 14.The computerized network apparatus of claim 11, wherein the at least onecomputer program is further configured to, when executed by theprocessor apparatus, cause the computerized network apparatus to:determine that one or more operational criteria are met within at leasta portion of an infrastructure of the network; and based at least on thedetermination, transmit data to the radio frequency transceiverapparatus causing a temporary change in allocation of the resources toat least one of the plurality of modem apparatus.
 15. The computerizednetwork apparatus of claim 10, wherein the evaluation of the receivedfirst data packets to generate characterization data relating aplurality of operational and configuration aspects of the wirelessaccess node comprises evaluation of at least: (i) a technology type usedby the wireless access node; (ii) a location of the wireless accessnode; and (iii) a number of user or client devices in active datacommunication with the wireless access node.
 16. The computerizednetwork apparatus of claim 15, wherein: the evaluation of the technologytype used by the wireless access node comprises evaluation of whetherthe wireless access node is capable of wireless operation compliant with3GPP (Third Generation Partnership Project) 5G NR (Fifth Generation NewRadio) Standards; the evaluation of a location of the wireless accessnode comprises determination of whether the wireless access node islocated within a designated hotspot or high activity area; and theevaluation of a number of user or client devices in active datacommunication with the wireless access node comprises determination of anumber of 3GPP UE (user equipment) operating in either RRC_Idle orRRC_Connected modes.
 17. Computerized wireless access node apparatus,comprising: at least one first packet data interface for interface witha radio frequency modulation/demodulation apparatus; at least onewireless interface for interface with one or more wireless user devices;processor apparatus in data communication with the at least one firstpacket data interface and the at least one wireless interface; andstorage apparatus in data communication with the processor apparatus,the storage apparatus comprising at least one computer programconfigured to, when executed by the processor apparatus, cause thecomputerized wireless access node apparatus to: transmit data relatingto at least one of a configuration or operational state of thecomputerized wireless access node apparatus to a network apparatus viathe radio frequency modulation/demodulation apparatus, the networkapparatus and radio frequency modulation/demodulation apparatuscommunicative via at least one wireline radio frequency channel, thetransmitted data configured to enable the network apparatus toselectively schedule data for delivery to the radio frequencymodulation/demodulation apparatus using a plurality of time-frequencyresources, the plurality of time-frequency resources selected as part ofa scheduling algorithm configured to also schedule respectivepluralities of time-frequency resources for others of a plurality ofradio frequency modulation/demodulation apparatus communicative with thenetwork apparatus based at least on respective data relating to aconfiguration of a computerized wireless access node apparatusassociated with respective ones of others of the plurality of radiofrequency modulation/demodulation apparatus.
 18. The computerizedwireless access node apparatus of claim 17, wherein: the radio frequencymodulation/demodulation apparatus comprises a cable modem within ahybrid fiber coax (HFC) network; the wireless access node comprises a3GPP-compliant NodeB; and the data relating to at least one of aconfiguration or operational state comprises data indicative of atleast: (i) a technology type used by the wireless access node; (ii) alocation of the wireless access node; and (ii) a number of user orclient devices in active data communication with the wireless accessnode.
 19. The computerized wireless access node apparatus of claim 17,wherein the data relating to at least one of a configuration oroperational state comprises data indicative of a weight or score derivedby the wireless access node based at least one the configuration oroperational state.
 20. The computerized wireless access node apparatusof claim 19, wherein the at least one computer program is furtherconfigured to, when executed by the processor apparatus, cause thecomputerized wireless access node apparatus to: generate a request forgrant of a temporary increase in resource allocation by the networkapparatus; and transmit the request to the network apparatus via theradio frequency modulation/demodulation apparatus in data communicationwith the wireless access node.